Systems and methods for processing meter information in a network of intelligent electronic devices

ABSTRACT

Systems and methods are provided for managing software scripts. One system comprises one or more meters, each configured to measure parameters of a commodity. The system also comprises a server and a plurality of client devices. The server is in communication with the one or more meters by way of a communication network and is configured to receive and store the measured parameters from the one or more meters. The client devices communicate with the server via the communication network. Also, the system includes a base device in communication with the client devices. The base device is configured to store one or more functional chains, each of the one or more functional chains comprising software code defining a plurality of functional actions to be performed in a specific sequence. The base device comprises an interface that allows the plurality of client devices to reference the functional chain.

PRIORITY

This application is a continuation-in-part application of U.S. patentapplication Ser. No. 13/644,877 filed on Oct. 4, 2012, entitled“INTELLIGENT ELECTRONIC DEVICE COMMUNICATION SOLUTIONS FOR NETWORKTOPOLOGIES”, which claims priority to U.S. Provisional PatentApplication No. 61/542,935, filed Oct. 4, 2011, the contents of both ofwhich are hereby incorporated by reference in their entireties.

This application is related to U.S. patent application Ser. No.13/799,832, filed Mar. 13, 2013, entitled “SYSTEMS AND METHODS FORCOLLECTING, ANALYZING, BILLING, AND REPORTING DATA FROM INTELLIGENTELECTRONIC DEVICES” and to U.S. patent application Ser. No. 13/831,708,filed Mar. 15, 2013, entitled “SYSTEMS AND METHODS FOR COLLECTING,ANALYZING, BILLING, AND REPORTING DATA FROM INTELLIGENT ELECTRONICDEVICES”, the contents of both of which are hereby incorporated byreference in their entireties.

BACKGROUND

1. Field

The present disclosure relates generally to intelligent electronicdevices (IEDs) and, in particular, to a system and method forsending/receiving data to/from intelligent electronic devices (IEDs) athigh speeds over a network. Additionally, the present disclosure relatesto an enterprise-wide energy management reporting, analysis, and billingsystem.

2. Description of the Related Art

Monitoring of electrical energy by consumers and providers of electricpower is a fundamental function within any electric power distributionsystem. Electrical energy may be monitored for purposes of usage,equipment performance and power quality. Electrical parameters that maybe monitored include volts, amps, watts, vars, power factor, harmonics,kilowatt hours, kilovar hours and any other power related measurementparameters. Typically, measurement of the voltage and current at alocation within the electric power distribution system may be used todetermine the electrical parameters for electrical energy flowingthrough that location.

Devices that perform monitoring of electrical energy may beelectromechanical devices, such as, for example, a residential billingmeter or may be an intelligent electronic device (“IED”). Intelligentelectronic devices typically include some form of a processor. Ingeneral, the processor is capable of using the measured voltage andcurrent to derive the measurement parameters. The processor operatesbased on a software configuration. A typical consumer or supplier ofelectrical energy may have many intelligent electronic devices installedand operating throughout their operations. IEDs may be positioned alongthe supplier's distribution path or within a customer's internaldistribution system. IEDs include revenue electric watt-hour meters,protection relays, programmable logic controllers, remote terminalunits, fault recorders and other devices used to monitor and/or controlelectrical power distribution and consumption. IEDs are widely availablethat make use of memory and microprocessors to provide increasedversatility and additional functionality. Such functionality includesthe ability to communicate with remote computing systems, either via adirect connection, e.g., a modem, a wireless connection or a network.IEDs also include legacy mechanical or electromechanical devices thathave been retrofitted with appropriate hardware and/or software allowingintegration with the power management system.

Typically, an IED is associated with a particular load or set of loadsthat are drawing electrical power from the power distribution system.The IED may also be capable of receiving data from or controlling itsassociated load. Depending on the type of IED and the type of load itmay be associated with, the IED implements a power management functionthat is able to respond to a power management command and/or generatepower management data. Power management functions include measuringpower consumption, controlling power distribution such as a relayfunction, monitoring power quality, measuring power parameters such asphasor components, voltage or current, controlling power generationfacilities, computing revenue, controlling electrical power flow andload shedding, or combinations thereof.

Conventional IEDs include the ability to communicate with remotecomputing systems. Traditionally, IEDs would transfer data using serialbased download commands. These commands would be accessed via an RS232,and RS485 or an Ethernet port encapsulating the serial request with anEthernet message using any Ethernet protocol such as HTTP or TCP/IP. Forinstance, host software or a “master” would make a request for a set ofdata from one or more memory registers in an IED slave. At that point,the IED slave would then communicate the data stored in the memoryregisters back to the host software utilizing a serial transfer. Thistechnology is inherently limited because host software traditionally islimited by the amount of memory registers that it would be able toaccept at any one time. For example, if the serial based protocol isModbus, a recognized industry standard protocol, most software mastersystems are limited by the protocol definition to 256 bytes of data thatcan be transferred at any one time. Thus, to pull large amount of data,many such requests would have to be sent to the IED or meter repeatedly.This would create many delays due to processing and data traffic.

SUMMARY

In accordance with embodiments of the present disclosure, there areprovided herein methods and systems for handling various types of meterinformation related to intelligent electronic devices (IEDs). Differentexternal devices, such as servers, PC clients, etc., may access thismeter information via a network interface.

According to one embodiment, a system for managing scripts (e.g.,software scripts) is provided, the system comprising one or more meters,each of the one or more meters configured to measure parameters of acommodity consumed at a customer location. The system also comprises aserver in communication with the one or more meters by way of acommunication network. The server may be configured to receive themeasured parameters from the one or more meters and store the parametersas log data. The system further includes a plurality of client devicesin communication with the server by way of the communication network anda base device in communication with the plurality of client devices byway of the communication network. The base device may be configured tostore one or more functional chains, each of the one or more functionalchains comprising software code defining a plurality of functionalactions to be performed in a specific sequence. The base devicecomprises an interface that allows the plurality of client devices toreference the functional chain. At least one of the plurality of clientdevices is a calling device that references the functional chain fromthe base device and executes the functional chain.

The present disclosure further defines systems for providing meterinformation. One embodiment includes a system that comprises a pluralityof meters, wherein each of the plurality of meters configured to measureparameters of a commodity consumed at a customer location. The systemalso comprises a server in communication with the plurality of meters byway of a network, wherein the server is configured to store the measuredparameters from the meters. The system also includes a plurality ofclient devices in communication with the server by way of the network,wherein the plurality of client devices include one or more callingdevices. The system further includes a storage device in communicationwith the plurality of client devices by way of the network, wherein thestorage device is configured to store meter information related to themeters. The meter information includes at least connection informationto be used to enable the one or more calling devices to access themeters. In addition, the one or more calling devices are configured toreference the storage device to inquire about one or more meters andreceive meter information related to the one or more meters.

Also described in the present disclosure are systems and methods formanaging meter connection parameters. In one embodiment, a systemcomprising a plurality of meters, a server, and a storage device. Eachmeter is configured to measure commodity data representing at least onecommodity being consumed at a location. The server is in communicationwith the plurality of meters via a network and is configured to storethe measured commodity data. The server is further configured to obtainmeter connection parameters related to the meters. The storage device isin communication with the server via the network and is configured toreceive the meter connection parameters from the server and store themeter connection parameters. The meter connection parameters enable aclient device connected to the network to identify at least one meterand communicate with the at least one meter.

The present disclosure further describes embodiments of a system thatcomprises a plurality of meters, a server, one or more client devices,and a “launchpad” device. Each meter is configured to measure commoditydata representing at least one commodity being consumed at a location.The server is in communication with the plurality of meters via anetwork and is configured to store the measured commodity data. The oneor more client devices are in communication with the server via thenetwork. The launchpad device is also in communication with the one ormore client devices via the network. In particular, the launchpad deviceexecutes a consolidated application that is configured to combine thefunctionality of a plurality of meter processing applications stored onthe one or more client devices.

In another embodiment, the IEDs, systems, network topologies and methodsthereof may be employed to implement an enterprise-wide energymanagement reporting, analysis and billing system. The system and methodof the present disclosure imports historical log energy usage data frommeters, IEDs and other sources and generates detailed and useful energyreports for analyzing energy use, planning and load curtailment. In oneembodiment, the system operates on a client/server architecture(although other architectures may be employed), where a server/settingseditor imports data from various sources enabling at least one client toaccess the data and generate reports therefrom. The system and methodenables multiple users to generate customized energy reports to studyenergy usage and demand enterprise-wide. For example, a user may beenabled to display Peak Energy Usage for the day, week, and month, orcompare usage between meters, locations, and customers. The system'sautomated billing module allows a user to generate sub-metering billsbased on customized rate structures for energy and other commoditiessuch as water and gas.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other objects, features and advantages of the presentdisclosure will be apparent from a consideration of the followingDetailed Description considered in conjunction with the drawing Figures,in which:

FIG. 1 is a block diagram of an intelligent electronic device (IED),according to an embodiment of the present disclosure.

FIGS. 2A-2H illustrate exemplary form factors for an intelligentelectronic device (IED) in accordance with an embodiment of the presentdisclosure.

FIG. 3 illustrates an environment in which the present disclosure may beutilized.

FIG. 4 is a block diagram of a web server power quality and revenuemeter, according to an embodiment of the present disclosure.

FIG. 5 is a functional block diagram of the processor of the web serverpower quality and revenue meter system shown in FIG. 4, according to theembodiment of the present invention.

FIG. 6 illustrates another environment in which the present disclosuremay be utilized.

FIG. 7 is a flow chart illustrating a method for communicating data froman IED on an internal network to a server on an external network througha firewall.

FIG. 8 illustrates yet another environment in which the presentdisclosure may be utilized.

FIG. 9 illustrates a further environment in which the present disclosuremay be utilized.

FIG. 10 illustrates an energy management reporting, analysis and billingsystem in accordance with an embodiment of the present disclosure.

FIG. 11 illustrates another environment in which the present disclosuremay be utilized.

FIGS. 12-33 illustrate various aspects of functional actions, functionalchains, triggers, and scripts.

FIGS. 34 and 35 illustrate portions of a frontend user interface fordisplaying aspects of functional chains.

FIG. 36 illustrates a portion of a frontend user interface for enablinga user to create a functional chain.

FIGS. 37 and 38 illustrate systems for managing meter information inaccordance with several embodiments of the present disclosure.

FIG. 39 illustrates an environment for storing connection informationfor known device in accordance with an embodiment of the presentdisclosure.

FIG. 40 illustrates an environment for device registration in accordancewith an embodiment of the present disclosure.

FIG. 41 illustrates an environment for scanning for devices inaccordance with an embodiment of the present disclosure.

FIG. 42 illustrates a radial menu in accordance with an embodiment ofthe present disclosure

DETAILED DESCRIPTION

Embodiments of the present disclosure will be described herein belowwith reference to the accompanying drawings. In the followingdescription, well-known functions or constructions are not described indetail to avoid obscuring the present disclosure in unnecessary detail.The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any configuration or design described hereinas “exemplary” is not necessarily to be construed as preferred oradvantageous over other configurations or designs. Herein, the phrase“coupled” is defined to mean directly connected to or indirectlyconnected with through one or more intermediate components. Suchintermediate components may include both hardware and software basedcomponents.

It is further noted that, unless indicated otherwise, all functionsdescribed herein may be performed in either hardware or software, orsome combination thereof. In one embodiment, however, the functions areperformed by at least one processor, such as a computer or an electronicdata processor, digital signal processor or embedded micro-controller,in accordance with code, such as computer program code, software, and/orintegrated circuits that are coded to perform such functions, unlessindicated otherwise.

It should be appreciated that the present disclosure can be implementedin numerous ways, including as a process, an apparatus, a system, adevice, a method, or a computer readable medium such as a computerreadable storage medium or a computer network where program instructionsare sent over optical or electronic communication links.

Embodiments of the present disclosure will be described herein belowwith reference to the accompanying drawings.

As used herein, intelligent electronic devices (“IEDs”) sense electricalparameters and compute data and can be any device including, but notlimited to, Programmable Logic Controllers (“PLC's”), Remote TerminalUnits (“RTU's”), electric power meters, panel meters, protective relays,fault recorders, phase measurement units, serial switches, smartinput/output devices and other devices which are coupled with powerdistribution networks to manage and control the distribution andconsumption of electrical power. A meter is a device that records andmeasures power events, power quality, current, voltage waveforms,harmonics, transients and other power disturbances. Revenue accuratemeters (“revenue meter”) relate to revenue accuracy electrical powermetering devices with the ability to detect, monitor, report, quantifyand communicate power quality information about the power that they aremetering.

FIG. 1 is a block diagram of an intelligent electronic device (IED) 10for monitoring and determining power usage and power quality for anymetered point within a power distribution system and for providing adata transfer system for faster and more accurate processing of revenueand waveform analysis.

The IED 10 of FIG. 1 includes a plurality of sensors 12 coupled tovarious phases A, B, C and neutral N of an electrical distributionsystem 11, a plurality of analog-to-digital (A/D) converters 14,including inputs coupled to the sensor 12 outputs, a power supply 16, avolatile memory 18, a non-volatile memory 20, a multimedia userinterface 22, and a processing system that includes at least one centralprocessing unit (CPU) 50 (or host processor) and one or more digitalsignal processors, two of which are shown, i.e., DSP1 60 and DSP2 70.The IED 10 also includes a Field Programmable Gate Array 80 whichperforms a number of functions, including, but not limited to, acting asa communications gateway for routing data between the various processors50, 60, 70, receiving data from the A/D converters 14 performingtransient detection and capture and performing memory decoding for CPU50 and the DSP processor 60. In one embodiment, the FPGA 80 isinternally comprised of two dual port memories to facilitate the variousfunctions. It is to be appreciated that the various components shown inFIG. 1 are contained within housing 90. Exemplary housings will bedescribed below in relation to FIGS. 2A-2H.

The plurality of sensors 12 sense electrical parameters, e.g., voltageand current, on incoming lines, (i.e., phase A, phase B, phase C,neutral N), from an electrical power distribution system 11 e.g., anelectrical circuit. In one embodiment, the sensors 12 will includecurrent transformers and potential transformers, wherein one currenttransformer and one voltage transformer will be coupled to each phase ofthe incoming power lines. A primary winding of each transformer will becoupled to the incoming power lines and a secondary winding of eachtransformer will output a voltage representative of the sensed voltageand current. The output of each transformer will be coupled to the A/Dconverters 14 configured to convert the analog output voltage from thetransformer to a digital signal that can be processed by the CPU 50,DSP1 60, DSP2 70, FPGA 80 or any combination thereof.

A/D converters 14 are respectively configured to convert an analogvoltage output to a digital signal that is transmitted to a gate array,such as Field Programmable Gate Array (FPGA) 80. The digital signal isthen transmitted from the FPGA 80 to the CPU 50 and/or one or more DSPprocessors 60, 70 to be processed in a manner to be described below.

The CPU 50 or DSP Processors 60, 70 are configured to operativelyreceive digital signals from the A/D converters 14 (see FIG. 1) toperform calculations necessary to determine power usage and to controlthe overall operations of the IED 10. In some embodiments, CPU 50, DSP160 and DSP2 70 may be combined into a single processor, serving thefunctions of each component. In some embodiments, it is contemplated touse an Erasable Programmable Logic Device (EPLD) or a ComplexProgrammable Logic Device (CPLD) or any other programmable logic devicein place of the FPGA 80. In some embodiments, the digital samples, whichare output from the A/D converters 14, are sent directly to the CPU 50or DSP processors 60, 70, effectively bypassing the FPGA 80 as acommunications gateway.

The power supply 16 provides power to each component of the IED 10. Inone embodiment, the power supply 16 is a transformer with its primarywindings coupled to the incoming power distribution lines and havingwindings to provide a nominal voltage, e.g., 5 VDC, +12 VDC and −12 VDC,at its secondary windings. In other embodiments, power may be suppliedfrom an independent power source to the power supply 16. For example,power may be supplied from a different electrical circuit or anuninterruptible power supply (UPS).

In one embodiment, the power supply 16 can be a switch mode power supplyin which the primary AC signal will be converted to a form of DC signaland then switched at high frequency, such as, for example, 100 Khz, andthen brought through a transformer to step the primary voltage down to,for example, 5 Volts AC. A rectifier and a regulating circuit would thenbe used to regulate the voltage and provide a stable DC low voltageoutput. Other embodiments, such as, but not limited to, linear powersupplies or capacitor dividing power supplies are also contemplated.

The multimedia user interface 22 is shown coupled to the CPU 50 in FIG.1 for interacting with a user and for communicating events, such asalarms and instructions to the user. The multimedia user interface 22may include a display for providing visual indications to the user. Thedisplay may be embodied as a touch screen, a liquid crystal display(LCD), a plurality of LED number segments, individual light bulbs or anycombination. The display may provide information to the user in the formof alpha-numeric lines, computer-generated graphics, videos, animations,etc. The multimedia user interface 22 further includes a speaker oraudible output means for audibly producing instructions, alarms, data,etc. The speaker is coupled to the CPU 50 via a digital-to-analogconverter (D/A) for converting digital audio files stored in a memory 18or non-volatile memory 20 to analog signals playable by the speaker. Anexemplary interface is disclosed and described in commonly owned pendingU.S. application Ser. No. 11/589,381, entitled “POWER METER HAVINGAUDIBLE AND VISUAL INTERFACE”, which claims priority to expired U.S.Provisional Patent Appl. No. 60/731,006, filed Oct. 28, 2005, thecontents of which are hereby incorporated by reference in theirentireties.

The IED 10 will support various file types including but not limited toMicrosoft Windows Media Video files (.wmv), Microsoft Photo Story files(.asf), Microsoft Windows Media Audio files (.wma), MP3 audio files(.mp3), JPEG image files (.jpg, .jpeg, .jpe, .jfif), MPEG movie files(.mpeg, .mpg, .mpe, .mlv, .mp2v .mpeg2), Microsoft Recorded TV Showfiles (.dvr-ms), Microsoft Windows Video files (.avi) and MicrosoftWindows Audio files (.wav).

The IED 10 further comprises a volatile memory 18 and a non-volatilememory 20. In addition to storing audio and/or video files, volatilememory 18 will store the sensed and generated data for furtherprocessing and for retrieval when called upon to be displayed at the IED10 or from a remote location. The volatile memory 18 includes internalstorage memory, e.g., random access memory (RAM), and the non-volatilememory 20 includes removable memory such as magnetic storage memory;optical storage memory, e.g., the various types of CD and DVD media;solid-state storage memory, e.g., a CompactFlash card, a Memory Stick,SmartMedia card, MultiMediaCard (MMC), SD (Secure Digital) memory; orany other memory storage that exists currently or will exist in thefuture. By utilizing removable memory, an IED can be easily upgraded asneeded. Such memory will be used for storing historical trends, waveformcaptures, event logs including time-stamps and stored digital samplesfor later downloading to a client application, web-server or PCapplication.

In a further embodiment, the IED 10 will include a communication device24, also know as a network interface, for enabling communicationsbetween the IED or meter, and a remote terminal unit, programmable logiccontroller and other computing devices, microprocessors, a desktopcomputer, laptop computer, other meter modules, etc. The communicationdevice 24 may be a modem, network interface card (NIC), wirelesstransceiver, etc. The communication device 24 will perform itsfunctionality by hardwired and/or wireless connectivity. The hardwireconnection may include but is not limited to hard wire cabling e.g.,parallel or serial cables, RS232, RS485, USB cable, Firewire (1394connectivity) cables, Ethernet, and the appropriate communication portconfiguration. The wireless connection will operate under any of thevarious wireless protocols including but not limited to Bluetooth™interconnectivity, infrared connectivity, radio transmissionconnectivity including computer digital signal broadcasting andreception commonly referred to as Wi-Fi or 802.11.X (where x denotes thetype of transmission), satellite transmission or any other type ofcommunication protocols, communication architecture or systems currentlyexisting or to be developed for wirelessly transmitting data includingspread spectrum 900 MHz, or other frequencies, Zigbee, WiFi, or any meshenabled wireless communication.

The IED 10 may communicate to a server or other computing device via thecommunication device 24. The IED 10 may be connected to a communicationsnetwork, e.g., the Internet, by any means, for example, a hardwired orwireless connection, such as dial-up, hardwired, cable, DSL, satellite,cellular, PCS, wireless transmission (e.g., 802.11a/b/g), etc. It is tobe appreciated that the network may be a local area network (LAN), widearea network (WAN), the Internet or any network that couples a pluralityof computers to enable various modes of communication via networkmessages. Furthermore, the server will communicate using variousprotocols such as Transmission Control Protocol/Internet Protocol(TCP/IP), File Transfer Protocol (FTP), Hypertext Transfer Protocol(HTTP), etc. and secure protocols such as Hypertext Transfer ProtocolSecure (HTTPS), Internet Protocol Security Protocol (IPSec),Point-to-Point Tunneling Protocol (PPTP), Secure Sockets Layer (SSL)Protocol, etc. The server will further include a storage medium forstoring a database of instructional videos, operating manuals, etc., thedetails of which will be described in detail below.

In an additional embodiment, the IED 10 will also have the capability ofnot only digitizing waveforms, but storing the waveform and transferringthat data upstream to a central computer, e.g., a remote server, when anevent occurs such as a voltage surge or sag or a current short circuit.This data will be triggered and captured on an event, stored to memory,e.g., non-volatile RAM, and additionally transferred to a host computerwithin the existing communication infrastructure either immediately inresponse to a request from a remote device or computer to receive saiddata in response to a polled request. The digitized waveform will alsoallow the CPU 50 to compute other electrical parameters such asharmonics, magnitudes, symmetrical components and phasor analysis. Usingthe harmonics, the IED 10 will also calculate dangerous heatingconditions and can provide harmonic transformer derating based onharmonics found in the current waveform.

In a further embodiment, the IED 10 will execute an e-mail client andwill send e-mails to the utility or to the customer direct on anoccasion that a power quality event occurs. This allows utilitycompanies to dispatch crews to repair the condition. The data generatedby the meters are use to diagnose the cause of the condition. The datais transferred through the infrastructure created by the electricalpower distribution system. The email client will utilize a POP3 or otherstandard mail protocol. A user will program the outgoing mail server andemail address into the meter. An exemplary embodiment of said meteringis available in U.S. Pat. No. 6,751,563, which all contents thereof areincorporated by reference herein.

The techniques of the present disclosure can be used to automaticallymaintain program data and provide field wide updates upon which IEDfirmware and/or software can be upgraded. An event command can be issuedby a user, on a schedule or by digital communication that will triggerthe IED 10 to access a remote server and obtain the new program code.This will ensure that program data will also be maintained allowing theuser to be assured that all information is displayed identically on allunits.

It is to be understood that the present disclosure may be implemented invarious forms of hardware, software, firmware, special purposeprocessors, or a combination thereof. The IED 10 also includes anoperating system and micro instruction code. The various processes andfunctions described herein may either be part of the micro instructioncode or part of an application program (or a combination thereof) whichis executed via the operating system.

It is to be further understood that because some of the constituentsystem components and method steps depicted in the accompanying figuresmay be implemented in software, or firmware, the actual connectionsbetween the system components (or the process steps) may differdepending upon the manner in which the present disclosure is programmed.Given the teachings of the present disclosure provided herein, one ofordinary skill in the related art will be able to contemplate these andsimilar implementations or configurations of the present disclosure.

Furthermore, it is to be appreciated that the components and devices ofthe IED 10 of FIG. 1 may be disposed in various housings depending onthe application or environment. For example, the IED 10 may beconfigured as a panel meter 900 as shown in FIGS. 2A and 2B. The panelmeter 900 of FIGS. 2A and 2B is described in more detail in commonlyowned U.S. Pat. No. 7,271,996, the contents of which are herebyincorporated by reference. As seen in FIGS. 2A and 2B, the IED 900includes a housing 902 defining a front surface 902 a, a rear surface902 b, a top surface 902 c, a bottom surface 902 d, a right side surface902 e, and a left side surface (not shown). Electrical device 900includes a face plate 904 operatively connected to front surface 902 aof housing 902. Face plate 904 includes displays 906, indicators 908(e.g., LEDs and the like), buttons 910, and the like providing a userwith an interface for visualization and operation of electrical device100. For example, as seen in FIG. 2A, face plate 904 of electricaldevice 900 includes analog and/or digital displays 906 capable ofproducing alphanumeric characters. Face plate 904 includes a pluralityof indicators 908 which, when illuminated, indicate to the user the“type of reading”, the “% of load bar”, the “parameter designation”which indicates the reading which is being displayed on displays 906, a“scale selector” (e.g., Kilo or Mega multiplier of Displayed Readings),etc. Face plate 904 includes a plurality of buttons 910 (e.g., a “menu”button, an “enter” button, a “down” button, a “right” button, etc.) forperforming a plurality of functions, including but not limited to:viewing of meter information; entering display modes; configuringparameters; performing re-sets; performing LED checks; changingsettings; viewing parameter values; scrolling parameter values; andviewing limit states. The housing 902 includes voltage connections orinputs 912 provided on rear surface 902 b thereof, and current inputs914 provided along right side surface 902 e thereof. The IED 900 mayinclude a first interface or communication port 916 for connection to amaster and/or slave device. Desirably, first communication port 916 issituated in rear surface 902 b of housing 902. IED 900 may also includea second interface or communication port 918 situated on face plate 904.

In other embodiment, the IED 10 may be configured as a socket meter 920,also known as a S-base type meter or type S meter, as shown in FIGS. 2Cand 2D. The socket meter 920 of FIGS. 2C and 2D is described in moredetail in commonly owned application Ser. No. 12/578,062 (U.S.Publication No. 2010/0090680), the contents of which are herebyincorporated by reference. Referring to FIGS. 2C and 2D, the meter 920includes a main housing 922 surrounded by a cover 924. The cover 924 ispreferably made of a clear material to expose a display 926 disposed onthe main body 922. An interface 928 to access the display and acommunication port 930 is also provided and accessible through the cover924. The meter 920 further includes a plurality of current terminals 932and voltage terminals 934 disposed on backside of the meter extendingthrough a base 935. The terminals 932, 934 are designed to mate withmatching jaws of a detachable meter-mounting device, such as a revenuemeter socket. The socket is hard wired to the electrical circuit and isnot meant to be removed. To install an S-base meter, the utility needonly plug in the meter into the socket. Once installed, a socket-sealingring 936 is used as a seal between the meter 920 and/or cover 924 andthe meter socket to prevent removal of the meter and to indicatetampering with the meter.

In a further embodiment, the IED 10 of FIG. 1 may be disposed in aswitchboard or draw-out type housing 940 as shown in FIGS. 2E and 2F,where FIG. 2E is a front view and FIG. 2F is a rear view. Theswitchboard enclosure 942 usually features a cover 944 with atransparent face 946 to allow the meter display 948 to be read and theuser interface 950 to be interacted with by the user. The cover 944 alsohas a sealing mechanism (not shown) to prevent unauthorized access tothe meter. A rear surface 952 of the switchboard enclosure 942 providesconnections for voltage and current inputs 954 and for variouscommunication interfaces 956. Although not shown, the meter disposed inthe switchboard enclosure 942 may be mounted on a draw-out chassis whichis removable from the switchboard enclosure 942. The draw-out chassisinterconnects the meter electronics with the electrical circuit. Thedraw-out chassis contains electrical connections which mate withmatching connectors 954, 956 disposed on the rear surface 952 of theenclosure 942 when the chassis is slid into place.

In yet another embodiment, the IED 10 of FIG. 1 may be disposed in anA-base or type A housing as shown in FIGS. 2G and 2H. A-base meters 960feature bottom connected terminals 962 on the bottom side of the meterhousing 964. These terminals 962 are typically screw terminals forreceiving the conductors of the electric circuit (not shown). A-basemeters 960 further include a meter cover 966, meter body 968, a display970 and input/output means 972. Further, the meter cover 966 includes aninput/output interface 974. The cover 966 encloses the meter electronics968 and the display 970. The cover 966 has a sealing mechanism (notshown) which prevents unauthorized tampering with the meter electronics.

It is to be appreciated that other housings and mounting schemes, e.g.,circuit breaker mounted, are contemplated to be within the scope of thepresent disclosure.

FIG. 3 illustrates an exemplary environment 100 in which the presentdisclosure may be practiced. The network 120 may be the Internet, apublic or private intranet, an extranet, wide area network (WAN), localarea network (LAN) or any other network configuration to enable transferof data and commands. An example network configuration uses theTransport Control Protocol/Internet Protocol (“TCP/IP”) network protocolsuite; however, other Internet Protocol based networks are contemplatedby the present disclosure. Communications may also include IP tunnelingprotocols such as those that allow virtual private networks couplingmultiple intranets or extranets together via the Internet. The network120 may support existing or envisioned application protocols, such as,for example, telnet, POP3, Mime, HTTP, HTTPS, PPP, TCP/IP, SMTP,proprietary protocols, or any other network protocols. During operation,the IED 110 may communicate using the network 120 as will be hereinafterdiscussed.

It is to be appreciated that there are at least two basic types ofnetworks, based on the communication patterns between the machines:client/server networks and peer-to-peer networks. On a client/servernetwork, every computer, device or IED has a distinct role: that ofeither a client or a server. A server is designed to share its resourcesamong the client computers on the network. A dedicated server computeroften has faster processors, more memory, and more storage space than aclient because it might have to service dozens or even hundreds of usersat the same time. High-performance servers typically use from two toeight processors (which does not include multi-core CPUs), have manygigabytes of memory installed, and have one or more server-optimizednetwork interface cards (NICs), RAID (Redundant Array of IndependentDrives) storage consisting of multiple drives, and redundant powersupplies. Servers often run a special network OS—such as Windows Server,Linux, or UNIX—that is designed solely to facilitate the sharing of itsresources. These resources can reside on a single server or on a groupof servers. When more than one server is used, each server can“specialize” in a particular task (file server, print server, faxserver, email server, and so on) or provide redundancy (duplicateservers) in case of server failure. For demanding computing tasks,several servers can act as a single unit through the use of parallelprocessing. A client device typically communicates only with servers,not with other clients. A client system is a standard PC that is runningan OS such as Windows. Current operating systems contain client softwarethat enables the client computers to access the resources that serversshare. Older operating systems, such as Windows 3.x and DOS, requiredadd-on network client software to join a network. By contrast, on apeer-to-peer network, every computer or device is equal and cancommunicate with any other computer or device on the network to which ithas been granted access rights. Essentially, every computer or device ona peer-to-peer network can function as both a server and a client; anycomputer or device on a peer-to-peer network is considered a server ifit shares a printer, a folder, a drive, or some other resource with therest of the network. Note that the actual networking hardware (interfacecards, cables, and so on) is the same in both client/server networks andpeer-to-peer networks. Only the logical organization, management, andcontrol of the networks vary.

The PC client 102 may comprise any computing device, such as a server,mainframe, workstation, personal computer, hand held computer, laptoptelephony device, network appliance, other IED, Programmable LogicController, Power Meter, Protective Relay etc. The PC client 102includes system memory 104, which may be implemented in volatile and/ornon-volatile devices. One or more client applications 106, which mayexecute in the system memory 104, are provided. Such client applicationsmay include, for example, FTP client applications. File TransferProtocol (FTP) is an application for transfer of files between computersattached to Transmission Control Protocol/Internet Protocol (TCP/IP)networks, including the Internet. FTP is a “client/server” application,such that a user runs a program on one computer system, the “client”,which communicates with a program running on another computer system,the “server”. Additionally, user interfaces 108 may be included fordisplaying system configuration, retrieved data and diagnosticsassociated with the IED 110.

The intelligent electronic device (IED) 110, in one embodiment, iscomprised of at least an FTP Server 131 including a Virtual Command FileProcessor 133, a File System and Driver 135, a non-volatile memory 137and a virtual data store 139. Of course, the IED 110 may contain otherhardware/software for performing functions associated with the IED;however, many of these functions have been described above with respectto FIG. 1 and will therefore not be further discussed.

IED 110 runs the FTP Server 131 as an independent process in theoperating system, allowing it to function independently of the otherrunning processes. Additionally, it allows for multiple connections,using the port/socket architecture of TCP/IP.

By running the FTP Server 131 as an independent process, this means thatother systems, such as a Modbus TCP handler, can run on IED 110concurrently with the FTP Server 131. This also means that multiple FTPconnections can be made with the only limitation being the system'savailable resources.

The FTP Server 131 provides access to the file system 135 of the IED 110on the standard FTP port (port 21). When a connection is made, PC client102 sends an FTP logon sequence, which includes a USER command and aPASS command. The PC client 102 then interacts with the IED 110,requesting information and writing files, ending in a logout.

The FTP Server 131 uses two ports for all actions. The first port 21, isa clear ASCII telnet channel, and is called the command channel. Thesecond port, which can have a different port number in differentapplications, is initiated whenever it is necessary to transfer data inclear binary, and is called the data channel.

The virtual data store 139 is an ideal storage medium for files that arewritten to very frequently, such as, for example, status information,diagnostics, and virtual command files. In contrast to these types offiles are files which require more long term storage, such as, forexample, logs, settings, and configurations, more suitably stored usinga compact flash drive.

The File Transfer Protocol (FTP) (Port 21) is a network protocol used totransfer data from one computer to another through a network, such asover the Internet. FTP is a commonly used protocol for exchanging filesover any TCP/IP based network to manipulate files on another computer onthat network regardless of which operating systems are involved (if thecomputers permit FTP access). There are many existing FTP client andserver programs. FTP servers can be set up anywhere between gameservers, voice servers, internet hosts, and other physical servers.

FTP runs exclusively over TCP. FTP servers by default listen on port 21for incoming connections from FTP clients. A connection to this portfrom the FTP Client forms the control stream on which commands arepassed to the FTP server from the FTP client and on occasion from theFTP server to the FTP client. FTP uses out-of-band control, which meansit uses a separate connection for control and data. Thus, for the actualfile transfer to take place, a different connection is required which iscalled the data stream. Depending on the transfer mode, the process ofsetting up the data stream is different.

In active mode, the FTP client opens a dynamic port (49152-65535), sendsthe FTP server the dynamic port number on which it is listening over thecontrol stream and waits for a connection from the FTP server. When theFTP server initiates the data connection to the FTP client it binds thesource port to port 20 on the FTP server.

To use active mode, the client sends a PORT command, with the IP andport as argument. The format for the IP and port is “h1,h2,h3,h4,p1,p2”.Each field is a decimal representation of 8 bits of the host IP,followed by the chosen data port. For example, a client with an IP of192.168.0.1, listening on port 49154 for the data connection will sendthe command “PORT 192,168,0,1,192,2”. The port fields should beinterpreted as p1×256+p2=port, or, in this example, 192×256+2=49154.

In passive mode, the FTP server opens a dynamic port (49152-65535),sends the FTP client the server's IP address to connect to and the porton which it is listening (a 16 bit value broken into a high and lowbyte, like explained before) over the control stream and waits for aconnection from the FTP client. In this case the FTP client binds thesource port of the connection to a dynamic port between 49152 and 65535.

To use passive mode, the client sends the PASV command to which theserver would reply with something similar to “227 Entering Passive Mode(127,0,0,1,192,52)”. The syntax of the IP address and port are the sameas for the argument to the PORT command.

In extended passive mode, the FTP server operates exactly the same aspassive mode, except that it only transmits the port number (not brokeninto high and low bytes) and the client is to assume that it connects tothe same IP address that it was originally connected to.

The objectives of FTP are to promote sharing of files (computer programsand/or data), to encourage indirect or implicit use of remote computers,to shield a user from variations in file storage systems among differenthosts and to transfer data reliably, and efficiently.

In one embodiment of the present disclosure, the IED 110 has the abilityto provide an external PC client 102 with an improved data transfer ratewhen making data download requests of data stored within an IED. This isachieved by configuring the IED 110 to include an FTP server 131including a Virtual Command File Processor 133. An improved datatransfer rate from the IED 110 may be realized by the external PC client102 issuing virtual commands to the IED 110. In response, the IED 110processes the received virtual commands in the Virtual Command Fileprocessor 133 to construct FTP commands therefrom to be applied to anovel file system 135 of the IED 110, coupled to the FTP server 131,wherein the novel file system 135 is configured as a PC file structureamenable to receiving and responding to the constructed FTP commands.The Virtual command files and the novel file system 135 are discussed ingreater detail in co-pending application Ser. No. 12/061,979.

While FTP file transfer comprises one embodiment for encapsulating filesto improve a data transfer rate from an IED to external PC clients, thepresent disclosure contemplates the use of other file transferprotocols, such as the Ethernet protocol such as HTTP or TCP/IP forexample. Of course, other Ethernet protocols are contemplated for use bythe present disclosure. For example, for the purpose of security andfirewall access, it may be preferable to utilize HTTP file encapsulationas opposed to sending the data via FTP. In other embodiments, data canbe attached as an email and sent via SMTP, for example. Such a system isdescribed in a co-owned U.S. Pat. No. 6,751,563, titled “ElectronicEnergy meter”, the contents of which are incorporated herein byreference. In the U.S. Pat. No. 6,751,563, at least one processor of theIED or meter is configured to collect the at least one parameter andgenerate data from the sampled at least one parameter, wherein the atleast one processor is configured to act as a server for the IED ormeter and is further configured for presenting the collected andgenerated data in the form of web pages.

With reference to U.S. Pat. No. 6,751,563, FIG. 4 is a block diagram ofa web server power quality and revenue meter 210. The meter is connectedto monitor electric distribution power lines (not shown), to monitorvoltage and current at the point of connection. Included therein isdigital sampler 220 for digitally sampling the voltage and current ofthe power being supplied to a customer or monitored at the point of theseries connection in the power grid. Digital sampler 220 digitallysamples the voltage and current and performs substantially similarly tothe A/D converters 14 described above in relation to FIG. 1. The digitalsamples are then forwarded to processor 230 for processing. It is to beappreciated that the processor 230 may be a single processing unit or aprocessing assembly including at least one CPU 50, DSP1 60, DSP2 70 andFPGA 80, or any combination thereof. Also connected to processor 230 isexternal device interface 240 for providing an interface for externaldevices 250 to connect to meter 210. These external devices mightinclude other power meters, sub-station control circuitry, on/offswitches, etc. Processor 230 receives data packets from digital sampler220 and external devices 250, and processes the data packets accordingto user defined or predefined requirements. A memory 260 is connected toprocessor 230 for storing data packets and program algorithms, and toassist in processing functions of processor 230. These processingfunctions include the power quality data and revenue calculations, aswell as formatting data into different protocols which will be describedlater in detail. Processor 230 provides processed data to network 280through network interface 270. Network 280 can be the Internet, theWorld Wide Web (WWW), an intranet, a wide area network (WAN), or localarea network (LAN), among others. In one embodiment, the networkinterface converts the data to an Ethernet TCP/IP format. The use of theEthernet TCP/IP format allows multiple users to access the power meter210 simultaneously. In a like fashion, network interface 270 might becomprised of a modem, cable connection, or other devices that provideformatting functions. Computers 290-292 are shown connected to network280.

A web server program (web server) is contained in memory 260, andaccessed through network interface 270. The web server 210 provides realtime data through any known web server interface format. For example,popular web server interface formats consist of HTML and XML formats.The actual format of the programming language used is not essential tothe present disclosure, in that any web server format can beincorporated herein. The web server provides a user friendly interfacefor the user to interact with the meter 210. The user can have variousaccess levels to enter limits for e-mail alarms. Additionally, the usercan be provided the data in multiple formats including raw data, bargraph, charts, etc. The currently used HTML or XML programming languagesprovide for easy programming and user friendly user interfaces.

The processor 230 formats the processed data into various networkprotocols and formats. The protocols and formats can, for example,consist of the web server HTML or XML formats, Modbus TCP, RS-485, FTPor e-mail. Dynamic Host Configuration Protocol (DHCP) can also be usedto assign IP addresses. The network formatted data may then be availableto users at computers 290-292 through network 280, which connects tometer 210 at the network interface 270. In one embodiment, networkinterface 270 is an Ethernet interface that supports, for example, 100base-T or 10 base-T communications. This type of network interface cansend and receive data packets between WAN connections and/or LANconnections and the meter 210. This type of network interface allows forsituations, for example, where the web server 210 may be accessed by oneuser while another user is communicating via the Modbus TCP, and a thirduser may be downloading a stored data file via FTP. The ability toprovide access to the meter by multiple users, simultaneously, is agreat advantage over the prior art. This can allow for a utilitycompany's customer service personnel, a customer and maintenancepersonnel to simultaneously and interactively monitor and diagnosepossible problems with the power service.

FIG. 5 is a functional block diagram of processor 230 of the web serverpower quality and revenue meter system according to some embodiments ofthe present invention. Processor 230 is shown containing four mainprocessing functions. The functions shown are illustrative and not meantto be inclusive of all possible functions performed by processor 230.Power Quality and Revenue Metering functions (metering functions) 310consist of a complete set of functions which are needed for powerquality and revenue metering. Packet data collected by digital sampler220 is transmitted to processor 230. Processor 230 calculates, forexample, power reactive power, apparent power, and power factor. Themetering function 310 responds to commands via the network or otherinterfaces supported by the meter. External Device Routing Functions 330handle the interfacing between the external device 250 and meter 210.Raw data from external device 250 is fed into meter 210. The externaldevice 250 is assigned a particular address. If more than one externaldevice is connected to meter 210, each device will be assigned a uniqueparticular address. The Network Protocol Functions 350 of meter 210 areexecuted by processor 230 which executes multiple networking tasks thatare running concurrently. As shown in FIG. 5, these include, but are notlimited to, the following network tasks included in network protocolfunctions 350: e-mail 360, web server 370, Modbus TCP 380, FTP 390, andDHCP 300. The e-mail 360 network protocol function can be utilized tosend e-mail messages via the network 280 to a user to, for example,notify the user of an emergency situation or if the power consumptionreaches a user-set or pre-set high level threshold. As the processorreceives packets of data it identifies the network processing necessaryfor the packet by the port number associated with the packet. Theprocessor 230 allocates the packet to a task as a function of the portnumber. Since each task is running independently, the meter 210 canaccept different types of requests concurrently and process themtransparently from each other. For example, the web server may beaccessed by one user while another user is communicating via Modbus TCPand at the same time a third user may download a log file via FTP. TheNetwork to Meter Protocol Conversion Functions 340 are used to formatand protocol convert the different network protocol messages to a commonformat understood by the other functional sections of meter 210. Afterthe basic network processing of the packet of data, any “commands” ordata which are to be passed to other functional sections of meter 210are formatted and protocol converted to a common format for processingby the Network to Meter Protocol Conversion Functions 340. Similarly,commands or data coming from the meter for transfer over the network arepre-processed by this function into the proper format before being sentto the appropriate network task for transmission over the network. Inaddition, this function first protocol converts and then routes data andcommands between the meter and external devices.

Although the above described embodiments enable users outside of thenetwork the IED or meter is residing on to access the internal memory orserver of the IED or meter, IT departments commonly block this accessthrough a firewall to avoid access by dangerous threats into corporatenetworks. A firewall is a system designed to prevent unauthorized accessto or from a private network, e.g., an internal network of a building, acorporate network, etc. Firewalls can be implemented in both hardwareand software, or a combination of both. Firewalls are frequently used toprevent unauthorized Internet users from accessing private networksconnected to the Internet, especially intranets. All messages enteringor leaving the intranet pass through the firewall, which examines eachmessage and blocks those that do not meet the specified securitycriteria. A firewall may employ one or more of the following techniquesto control the flow of traffic in and of the network it isprotecting: 1) packet filtering: looks at each packet entering orleaving the network and accepts or rejects it based on user-definedrules; 2) Application gateway: applies security mechanisms to specificapplications, such as FTP and Telnet servers; 3) Circuit-level gateway:applies security mechanisms when a TCP or UDP connection is established;once the connection has been made, packets can flow between the hostswithout further checking; 4) Proxy server: intercepts all messagesentering and leaving the network, effectively hides the true networkaddresses; and 5) Stateful inspection: does not examine the contents ofeach packet but instead compares certain key parts of the packet to adatabase of trusted information; if the comparison yields a reasonablematch, the information is allowed through; otherwise it is discarded.Other techniques and to be developed techniques are contemplated to bewithin the scope of the present disclosure.

In one embodiment, the present disclosure provides for overcoming theproblem of not being allowed firewall access to an IED or meterinstalled within a facility, i.e., the meter is residing on a privatenetwork, by enabling an IED to initiate one way communication throughthe firewall. In this embodiment, the IED or meter posts the monitoredand generated data on an Internet site external to the corporate orprivate network, i.e., on the other side of a firewall. The benefit isthat any user would be able to view the data on any computer or webenabled smart device without having to pierce or bypass the firewall.Additionally, there is a business opportunity to host this data on a webserver and charge a user a monthly fee for hosting the data. Thefeatures of this embodiment can be incorporated into any telemetryapplication including vending, energy metering, telephone systems,medical devices and any application that requires remotely collectingdata and posting it on to a public Internet web site.

In one embodiment, the IED or metering device will communicate throughthe firewall using a protocol such as HTTP via a port that is openthrough the firewall. Referring to FIG. 6, IEDs or meters 410, 412 414reside on an internal network 416, e.g., an intranet, private network,corporate network, etc. The internal network 416 is coupled to anexternal network 422, e.g., the Internet, via a router 420 or similardevice over any known hardwire or wireless connection 421. A firewall418 is disposed between the internal network 416 and external network422 to prevent unauthorized access from outside the internal network 416to the IEDs or meters 410, 412, 414. Although the firewall 418 is shownbetween the internal network 416 and the router 420 it is to beappreciated that other configurations are possible, for example, thefirewall 418 being disposed between the router 420 and external network422. In other embodiments, the firewall 418 and router 420 may beconfigured as a single device. It is further to be appreciated thatfirewall 418 can be implemented in both hardware and software, or acombination of both.

The communication device or network interface of the meter (as describedabove in relation to FIG. 1) will communicate through the firewall 418and read a web site server 424. It is to be appreciated that the one waycommunication from the IED through the firewall may be enabled byvarious techniques, for example, by enabling outbound traffic to the IPaddress or domain name of the server 424 or by using a protocol that hasbeen configured, via the firewall settings, to pass through the firewallsuch as HTTP (Hyper Text Transfer Protocol), IP (Internet Protocol), TCP(Transmission Control Protocol), FTP (File Transfer Protocol), UDP (UserDatagram Protocol), ICMP (Internet Control Message Protocol), SMTP(Simple Mail Transport Protocol), SNMP (Simple Network ManagementProtocol), Telnet, etc. Alternatively, the IED may have exclusive accessto a particular port on the firewall, which is unknown to other users oneither the internal or external network. Other methods or techniques arecontemplated, for example, e-mail, HTTP tunneling, SNTP trap, MSN,messenger, IRQ, Twitter™, Bulletin Board System (BBS), forums, UniversalPlug and Play (UPnP), User Datagram Protocol (UDP) broadcast, UDPunicast, Virtual Private Networks (VPN), etc.

The server 424 will provide instructions in computer and/or humanreadable format to the IED or meter. For instance, the web server 424might have XML tags that state in computer readable format to providedata for the last hour on energy consumption by 15 minute intervals. Themeter 410, 412, 414 will then read those instructions on that web server424 and then post that data up on the server 424. In this manner, theIED or meter initiates communication in one direction, e.g., an outbounddirection, to the server 424.

Another server (or possibly the same server) will read the data that themeter 410, 412, 414 posts and will format the meter data into data thatcan be viewed for humans on a web site or a software application, i.e.,UI Server 426. Servers 424, 426 can also store the data in a database orperform or execute various control commands on the data. Clients 428 mayaccess the IED data stored or posted on servers 424, 426 via aconnection to the network 422.

Since the meters are only communicating in an outbound direction only,the meters 410, 412, 414 can read data or instructions from an externalnetwork application (e.g., server 424), but the external networkapplication cannot request information directly from the meter. Theserver 424 posts the data or instructions on the web site and waits forthe meter to check the site to see if there has been a new post, i.e.,new instructions for the meter. The meter can be programmed at theuser's discretion as to frequency for which the meter 410, 412, 414exits out to the external network to view the postings.

The meter instruction server 424 will post instructions in a directoryprogrammed/located on the server or into XML or in any fashion that themeter is configured to understand and then the meter will post whateverdata it is instructed to do. The meter can also be configured toaccomplish control commands. In addition to the meter instruction server424, a user interface (UI) server 426 is provided that can be used toenable a user interface to the user. The user can provide input on theUI server 426 that might trigger the meter instruction server 424 toproduce a message to control the energy next time the meter reads thatserver.

Referring to FIG. 7, a method for communicating data from an IED on aninternal network to a server on an external network through a firewallis illustrated. In step 452, the IED 410 communicates through thefirewall 418 to a predetermined server 424 on an external network 422.The IED 410 may be programmed to periodically communicate to the serverat predefined intervals. During this communication session, the IED 410reads instructions disposed in a directory or folder on thepredetermined server 424, step 454. Next, in step 456, the IED 410collects data from its internal memory or generates data based on theread instructions. The IED 410 then transmits the data to the server 424in a predetermined format, e.g., extensible markup language (XML),comma-separated value (CSV), etc., step 458. In step 460, thepredetermined server 424 posts the received data on a web siteaccessible from the external network 422. The data may be posted on theserver 424 or a UI (user interface) server 426 configured to providedata for end users, e.g., clients 428. It is to be appreciated that theUI server 426 may be configured to post data from several locations inone convenient interface for, for example, an organization managing theseveral locations. A provider of the servers 424, 426 may charge a feeto the end user for the hosting of the web site and providing the datain a convenient and accessible format.

In another embodiment, the IED or metering device will communicatethrough the firewall using a server 530 disposed on an internal networkprotected by a firewall. Referring to FIG. 8, IEDs or meters 510, 512,514 reside on an internal network 516, e.g., an intranet, privatenetwork, corporate network, etc. The internal network 516 is coupled toan external network 522, e.g., the Internet, via a router 520 or similardevice over any known hardwire or wireless connection 521. A firewall518 is disposed between the internal network 516 and external network522 to prevent unauthorized access from outside the internal network 516to the IEDs or meters 510, 512, 514. Although the firewall 518 is shownbetween the internal network 516 and the router 520 it is to beappreciated that other configurations are possible, for example, thefirewall 518 being disposed between the router 520 and external network522. In other embodiments, the firewall 518 and router 520 may beconfigured as a single device. It is further to be appreciated thatfirewall 518 can be implemented in both hardware and software, or acombination of both.

In this embodiment, server 530 aggregates data from the various IEDs510, 512, 514 coupled to the internal or private network 516. Since theserver 530 and the IEDs 510, 512, 514 are all on the same side of thefirewall 518, generally communications and data transfers among theserver 530 and the IEDs 510, 512, 514 is unrestricted. Server 530 thencommunicates or transfers the data from the IEDs to server 524 on theexternal network on the other side of the firewall 518. Thecommunication between servers 530 and 524 may be accomplished by any oneof the communication means or protocols described in the presentdisclosure. The server 524 then posts the data from the IEDs 510, 512,514 making the data accessible to clients 528 on external networks, asdescribed above.

In a further embodiment, the IED or metering device will communicatethrough the firewall using a server 630 disposed on an internal networkprotected by a firewall. Referring to FIG. 9, IEDs or meters 610, 612,614 reside on an internal network 616, e.g., an intranet, privatenetwork, corporate network, etc. The internal network 616 is coupled toan external network 622, e.g., the Internet, via a router 620 or similardevice over any known hardwire or wireless connection 621. A firewall618 is disposed between the internal network 616 and external network622 to prevent unauthorized access from outside the internal network 616to the IEDs or meters 610, 612, 614. Although the firewall 618 is shownbetween the internal network 616 and the router 620 it is to beappreciated that other configurations are possible, for example, thefirewall 618 being disposed between the router 620 and external network622. In other embodiments, the firewall 618 and router 620 may beconfigured as a single device. It is further to be appreciated thatfirewall 618 can be implemented in both hardware and software, or acombination of both.

In this embodiment, server 630 aggregates data from the various IEDs610, 612, 614 coupled to the internal or private network 616. Since theserver 630 and the IEDs 610, 612, 614 are all on the same side of thefirewall 618, generally communications and data transfers among theserver 630 and the IEDs 610, 612, 614 is unrestricted. Server 630 thencommunicates or transfers the data from the IEDs to clients 628 on theexternal network on the other side of the firewall 618. Thecommunication between server 630 and clients 628 may be accomplished byany one of the communication means or protocols described in the presentdisclosure.

In another embodiment, each IED 610, 612, 614 may be configured to actas a server to perform the functionality described above obviating theneed for server 630.

Furthermore in another embodiment, each IED 610, 612, 614 and eachclient device 628 may be configured as a server to create a peer-to-peernetwork, token ring or a combination of any such topology.

The systems and methods of the present disclosure may utilize one ormore protocols and/or communication techniques including, but notlimited to, e-mail, File Transfer Protocol (FTP), HTTP tunneling, SNTPtrap, MSN, messenger, IRQ, Twitter™, Bulletin Board System (BBS),forums, Universal Plug and Play (UPnP), User Datagram Protocol (UDP)broadcast, UDP unicast, Virtual Private Networks (VPN), etc.

In one non-limiting embodiment, each IED sends data to a recipient viaelectronic mail, also known as email or e-mail. An Internet emailmessage consists of three components, the message envelope, the messageheader, and the message body. The message header contains controlinformation, including, minimally, an originator's email address and oneor more recipient addresses. Usually descriptive information is alsoadded, such as a subject header field and a message submission date/timestamp. Network-based email was initially exchanged on the ARPANET inextensions to the File Transfer Protocol (FTP), but is now carried bythe Simple Mail Transfer Protocol (SMTP), first published as Internetstandard 10 (RFC 821) in 1982. In the process of transporting emailmessages between systems, SMTP communicates delivery parameters using amessage envelope separate from the message (header and body) itself.Messages are exchanged between hosts using the Simple Mail TransferProtocol with software programs called mail transfer agents (MTAs); anddelivered to a mail store by programs called mail delivery agents (MDAs,also sometimes called local delivery agents, LDAs). Users can retrievetheir messages from servers using standard protocols such as POP orIMAP, or, as is more likely in a large corporate environment, with aproprietary protocol specific to Novell Groupwise, Lotus Notes orMicrosoft Exchange Servers. Webmail interfaces allow users to accesstheir mail with any standard web browser, from any computer, rather thanrelying on an email client. Programs used by users for retrieving,reading, and managing email are called mail user agents (MUAs). Mail canbe stored on the client, on the server side, or in both places. Standardformats for mailboxes include Maildir and mbox. Several prominent emailclients use their own proprietary format and require conversion softwareto transfer email between them. Server-side storage is often in aproprietary format but since access is through a standard protocol suchas IMAP, moving email from one server to another can be done with anyMUA supporting the protocol.

In one embodiment, the IED composes a message using a mail user agent(MUA). The IED enters the email address of a recipient and sends themessage. The MUA formats the message in email format and uses theSubmission Protocol (a profile of the Simple Mail Transfer Protocol(SMTP), see RFC 6409) to send the message to the local mail submissionagent (MSA), for example, run by the IED's internet service provider(ISP). The MSA looks at the destination address provided in the SMTPprotocol (not from the message header). An Internet email address is astring of the form “recipient@meter.” The part before the “@” symbol isthe local part of the address, often the username of the recipient, andthe part after the “@” symbol is a domain name or a fully qualifieddomain name. The MSA resolves a domain name to determine the fullyqualified domain name of the mail exchange server in the Domain NameSystem (DNS). The DNS server for the domain responds with any MX recordslisting the mail exchange servers for that domain, for example, amessage transfer agent (MTA) server run by the recipient's ISP. The MSAsends the message to MTA using SMTP. This server may need to forward themessage to other MTAs before the message reaches the final messagedelivery agent (MDA). The MDA delivers it to the mailbox of therecipient. The recipient retrieves the message using either the PostOffice Protocol (POP3) or the Internet Message Access Protocol (IMAP4).

Other types of e-mail systems may also be employed, for example,web-based email, POP3 (Post Office Protocol 3) email services, IMAP(Internet Message Protocol) e-mail servers, and MAPI (MessagingApplication Programming Interface) email servers to name a few.

In a further embodiment, File Transfer Protocol (FTP) may be employed.Techniques for transferring data from an IED to a device is described incommonly owned pending U.S. patent application Ser. No. 12/061,979, thecontents of which are incorporated by reference.

In one embodiment, IEDs employ Universal Plug and Play (UPnP) protocol,which is a set of networking protocols that permits networked devices todiscover each other's presence, and notify clients of services availableon these devices. UPnP takes the form of UDP broadcast messages, whichare sent across a local network, to notify other devices of availableservices, and http requests to query the details of those devices andservices.

In one embodiment, UPnP is employed to allow the network addresses ofdevices, such as meters, to automatically be discovered by a client.This enables the client software to display a list of all devices whichare available. In addition, this could also allow the client software toenable the user to connect to these devices, without having to configurethe network address of that device. In addition, the UPnP notify may beused to indicate the health status of the device, including starting up,running, errors in configuration, and resetting.

In another embodiment, UPnP is employed to allow devices, such asmeters, to notify the clients of what services they support, such asModbus, dnp, web, ftp, log download, and data streaming. This could beextended by including information particular to that service orprotocol, such as to allow the client to interface with that servicewith no user input. This could enable the client software to display thedevice such that the user can focus on the details of the device, ratherthen worrying about the minutiae of connection information.

In another embodiment, an automated server is configured to performactions related to these automatically discovered services, such asretrieving real time information, downloading logs, or registering fornotification of events. For example, as shown in FIG. 8, a server 530could be on a network 516 to collect log information from meters 510,512, 514, and whenever a meter broadcast that it provided log data, theserver 530 could automatically collect that data from the meter. Asanother example, the server 530 could automatically poll and log thereal-time readings of all meters on the network, automatically includingthem as they become available on the network. As described above, theserver 530 may then post the data to server 524.

In one embodiment, HTTP tunneling is employed to send a message(including the IED's or meter's data) to a server, which listens forsuch messages, and parses out the IED's or meter's data. This could beperformed by embedding the meter's data in a HTTP message, which couldbe sent to the server, for example, server 424 as shown in FIG. 6. TheHTTP wrapper would allow this data to pass through firewalls which onlyallow web traffic. For example, in the architecture of FIG. 6, IED 410may send a HTTP message containing measured or calculated data throughfirewall 418 to server 424 or server 430. In another example as shown inFIG. 8, server 530 may collect data from the various IEDs 510, 512, 514and forward the collected data in a HTTP message through firewall 518 toserver 524.

It is to be appreciated that HTTP tunneling applies to systemarchitectures where a server is provided as the receiver of the IED ormeter data, as the clients would be unable to process such information.Referring to FIG. 9, server 630 is the destination (and collects) themessages generated from the various IEDs 610, 612, 614, but device 628is a client, and without server software, would be unable to receive themessages. However, by programming device 628 with server software, theclient device 628 becomes a server and can receive the messages.

It is further to be appreciated that the HTTP message can be sent basedon various triggers including, but not limited to, time-based trigger,event-based trigger, storage capacity based trigger, etc.

In another embodiment, the IEDs can communicate through to devices usinga Simple Network Management Protocol (SNMP) trap. SNMP traps enable anagent, e.g., an agent running on an IED, to notify a management station,e.g., a server, of significant events by way of an unsolicited SNMPmessage. Upon occurrence of an event, an agent that sends an unsolicitedor asynchronous trap to the network management system (NMS), also knownas a manager. After the manager receives the event, the manager displaysit and can choose to take an action based on the event. For instance,the manager can poll the agent or IED directly, or poll other associateddevice agents to get a better understanding of the event. For themanagement system to understand a trap sent to it by an agent, themanagement system must know what the object identifier (OID) of the trapor message defines. Therefore, the management system or server must havethe Management Information Base (MIB) for that trap loaded. Thisprovides the correct OID information so that the network managementsystem can understand the traps sent to it. Additionally, a device doesnot send a trap to a network management system unless it is configuredto do so. A device must know that it should send a trap. The trapdestination is usually defined by an IP address, but can be a host name,if the device is set up to query a Domain Name System (DNS) server.

Common chat protocols, such as MSN, AIM, IRQ, IRC, and Skype, could beused to send a message, containing the meter's data, to a public chatserver, e.g., server 440, 540, 640, which could then route that messageto any desired client. Another possible implementation could be to havea special client that listens for these messages, parses the datacontents, and presents them as another manner. In one embodiment, themessages are proprietary format Ethernet messages, typically sent overTCP. It is to be appreciated that the actual format depends on thespecific chat protocol.

A public social server that supports a common web interface for postinginformation, such as Twitter™, Facebook™, BBS's, could be used to post astatus, containing the meter's data, to a user on the public socialserver for that service, e.g., server 440, 540, 640. This post couldthen be viewed by the clients to see the meter's data, or read byanother server for further parsing and presentation. The data could beformatted as human readable text (e.g., “The voltage is 120.2 v”), asmachine parsable text (e.g., “voltage.an=120.2”), hex representingbinary data (e.g., “0152BF5E”). The HTTP interface could be used, whichwould work the same way as users updating it from their browser (HTTPpush). Some of these servers also provide a proprietary format Ethernetmessage, typically sent over TCP.

In one non-limiting example, a public social server such as the systememployed by Facebook may be utilized to post the IEDs data so the datais accessible on the external network outside of the firewall. Facebookuses a variety of services, tools and programming languages to make upits infrastructure which may be employed in the systems and methods ofthe present disclosure to implement the technique described herein. Inthe front end, the servers run a LAMP (Linux, Apache, MySQL and PHP)stack with Memcache. Linux is a Unix-like operating system kernel. It isopen source, highly customizable, and good for security. Facebook'sserver runs the Linux operating system Apache HTTP server. For thedatabase, Facebook uses MySQL for its speed and reliability. MySQL isused primarily as a key store of value when the data are randomlydistributed among a large number of cases logical. These logicalinstances extend across physical nodes and load balancing is done atphysical node. Facebook uses PHP, since it is a good web programminglanguage and is good for rapid iteration. PHP is a dynamically typedlanguage/interpreter. Memcache is a caching system that is used toaccelerate dynamic web sites with databases (like Facebook) by cachingdata and objects in RAM to reduce reading time. Memcache is the mainform of caching on Facebook and helps relieve the burden of database.Having a caching system allows Facebook to be as fast as it is toremember information. Furthermore, Facebook backend services are writtenin a variety of different programming languages like C++, Java, Python,and Erlang. Additionally, it employs the following services: 1.)Thrift—a lightweight remote procedure call framework for scalablecross-language services development, which supports C++, PHP, Python,Perl, Java, Ruby, Erlang, and others; 2.) Escribano (server logs)—aserver for aggregating log data streamed in real time on many otherservers, it is a scalable framework useful for recording a wide range ofdata; 3.) Cassandra (database)—a database designed to handle largeamounts of data spread out across many servers; 4.) HipHop for PHP—atransformer of source code for PHP script code and was created to saveserver resources, HipHop transforms PHP source code in C++ optimized,among others. It is to be appreciated that any of the above systems,devices and/or services may be implemented in the various architecturesdisclosed in the present disclosure to achieve the teaching andtechniques described herein.

A public web site, e.g., hosting on server 440, 540, 640, which allowsthe posting of information, such as a Forum, could be used to post amessage, containing the meter's data, to a group, thread, or otherlocation. This post would take place by a HTTP POST to the web site'sserver, where by the server would store that information, and present iton the web site. This message could then be viewed by the clients to seethe meter's data, or read by another server for further parsing andpresentation. The data could be formatted as human readable text (e.g.,“The voltage is 120.2 v”), as machine parsable text (e.g.,“voltage.an=120.2”), hex representing binary data (e.g., “0152BF5E”).The HTTP interface could be used, which would work the same way as usersupdating it from their browser (HTTP push).

User Datagram Protocol (UDP) messages could be used to send a messagefrom the IEDs or meters to a server, which listens for such messages,and parses out the meter's data. When employing UDP broadcasts, messagescould be sent from the IEDs or meters to a server, e.g., servers 530,630, since UDP broadcasts do not work across networks. The messagescontaining the IED's or meter's data can then be sent to externalnetworks via any of the described (or to be developed) communicationmethods. Alternatively, a UDP unicast could support sending to anyserver, e.g., server 424, 524.

A Virtual Private Network (VPN) could be created such that each meter onthe internal network is part of the same virtual private network as eachof the clients. A Virtual Private Network (VPN) is a technology forusing the Internet or another intermediate network to connect computersto isolated remote computer networks that would otherwise beinaccessible. A VPN provides security so that traffic sent through theVPN connection stays isolated from other computers on the intermediatenetwork. VPNs can connect individual IEDs or meters to a remote networkor connect multiple networks together. Through VPNs, users are able toaccess resources on remote networks, such as files, printers, databases,or internal websites. VPN remote users get the impression of beingdirectly connected to the central network via a point-to-point link. Anyof the other described (or to be developed) protocols could then be usedto push data to another server or clients on the VPN.

Hosted data services, such as a hosted database, cloud data storage,Drop-Box, or web service hosting, could be used as an external server tostore the meter's data. Hosted data services can be referred to asHosting. Each of these Hosts, e.g., servers 440, 540, 640, could then beaccessed by the clients to query the Hosted Data. Many of these hosteddata services support HTTP Push messages to upload the data, or directSQL messages. As many web service and cloud hosts allow their users touse their own software, a hosted data service could be further extendedby placing proprietary software on them, thus allowing them to act asthe external meter server for any of the previously mentioned methods(e.g., servers 424, 524).

In another embodiment, the IEDs can communicate to devices using GenericObject Oriented Substation Event (GOOSE) messages, as defined by theIEC-61850 standard, the content of which are herein incorporated byreference. A GOOSE message is a user-defined set of data that is“published” on detection of a change in any of the contained data itemssensed or calculated by the IED. Any IED or device on the LAN or networkthat is interested in the published data can “subscribe” to thepublisher's GOOSE message and subsequently use any of the data items inthe message as desired. As such, GOOSE is known as a Publish-Subscribemessage. With binary values, change detect is a False-to-True orTrue-to-False transition. With analog measurements, IEC61850 defines a“deadband” whereby if the analog value changes greater than the deadbandvalue, a GOOSE message with the changed analog value is sent. Insituation where changes of state are infrequent, a “keep alive” messageis periodically sent by the publisher to detect a potential failure. Inthe keep-alive message, there is a data item that indicates “The NEXTGOOSE will be sent in XX Seconds” (where XX is a user definable time).If the subscriber fails to receive a message in the specified timeframe, it can set an alarm to indicate either a failure of the publisheror the communication network.

The GOOSE message obtains high-performance by creating a mapping of thetransmitted information directly onto an Ethernet data frame. There isno Internet Protocol (IP) address and no Transmission Control Protocol(TCP). For delivery of the GOOSE message, an Ethernet address known as aMulticast address is used. A Multicast address is normally delivered toall devices on a Local Area Network (LAN). Many times, the message isonly meant for a few devices and doesn't need to be delivered to alldevices on the LAN. To minimize Ethernet traffic, the concept of a“Virtual” LAN or VLAN is employed. To meet the reliability criteria ofthe IEC-61850, the GOOSE protocol automatically repeats messages severaltimes without being asked. As such, if the first GOOSE message gets lost(corrupted), there is a very high probability that the next message orthe next or the next will be properly received.

It is to be appreciated that the above-described one-way communicationembodiments may apply to systems other than for energy metering. Forexample, the present disclosure may be applied to a vending machine orsystem, wherein the vending machine located in a building or structurehaving a private or corporate network. The vending machine will include,among other data collecting components, at least a communication deviceor network interface as described above. The communication device ornetwork interface will coupled the vending machine to the internalnetwork which may be further coupled to the Internet via a firewall. Thevending machine may vend or dispense a plurality of items, such as sodacans, candy bars, etc., similar to the vending machine described in U.S.Pat. No. 3,178,055, the contents of which are incorporated by reference.In accordance with the present disclosure, the vending machine willmonitor and collect data related to the items sold. Such data mayinclude quantities of items sold, a re-stock limit that has beenreached, total revenue generated by the vending machine, etc. In oneembodiment, the vending machine will post to a web site, residing on aserver outside of the internal network such as the Internet, quantitiesof specific items sold by the vending machine that are required to fillthe vending machine. In this manner, an operator that maintains thevending machine can check the web site before going to the location ofthe vending machine and know exactly how many items are required to fillthe vending machine before going to the location to refill the vendingmachine.

In another embodiment, the teachings of the present disclosure may beapplied to a medical device, for example, a medical monitoring deviceconfigured to be worn on a patient. In this embodiment, the medicalmonitoring device will include at least a communication device ornetwork interface as described above and monitor a certain parameterrelating to a patient, e.g., a heartbeat. In one embodiment, the atleast a communication device or network interface operates on a wirelessconnection and coupled the medical monitoring device to internal network(e.g., a home network) which may be further coupled to the Internet viaa firewall, e.g., a router provided by the Internet Service Provider. Atpredetermined intervals, the medical monitoring device will communicateto and post the monitored data on a remote website. A user such as adoctor may then view the data of the patient by accessing the web siteand not directly connecting to the medical monitoring device.

Other embodiments may include security systems such as fire alarmsystems, security alarm systems, etc., which need to report data. Alsoenvisioned are manufacturing sensing equipment, traffic sensingequipment, scientific instrumentation or other types of reportinginstrumentation.

Based on the sensitivity of the data being communicated and postedthrough the firewall to various external networks, various data securitytechniques are employed by the IEDs (e.g., meters, vending machines,medical monitoring device, etc.) contemplated by the present disclosure,some of which are described below.

The original FTP specification is an inherently insecure method oftransferring files because there is no method specified for transferringdata in an encrypted fashion. This means that under most networkconfigurations, user names, passwords, FTP commands and transferredfiles can be “sniffed” or viewed by anyone on the same network using apacket sniffer. This is a problem common to many Internet protocolspecifications written prior to the creation of SSL such as HTTP, SMTPand Telnet. The common solution to this problem is to use simplepassword protection or simple encryption schemes, or more sophisticatedapproaches using either SFTP (SSH File Transfer Protocol), or FTPS (FTPover SSL), which adds SSL or TLS encryption to FTP as specified in RFC4217. The inventors have contemplated the use of each of these schemesin the IEDs described above.

In one embodiment, the FTP server 131 in the IED 110 shown in FIG. 3uses a set of username and passwords which are programmed throughModbus. These username and passwords can only be programmed when a userperforms a logon with administrative rights. Each programmed useraccount can be given differing permissions, which grant or restrictaccess to different roles within the file system. Each role controlsread and write access to specific files and directories within the filesystem through FTP. These roles can be combined to customize the accessa specific user is given. When passwords are disabled by the user, adefault user account is used, with full permissions, and a username andpassword of “anonymous”.

Password protection schemes are measured in terms of their passwordstrength which may be defined as the amount of resiliency a passwordprovides against password attacks. Password strength can be measured inbits of entropy. Password strength is an important component of anoverall security posture, but as with any component of security, it isnot sufficient in itself. Strong passwords can still be exploited byinsider attacks, phishing, keystroke login, social engineering, dumpsterdiving, or systems with vulnerabilities that allow attackers in withoutpasswords. To overcome these drawbacks it is contemplated to use someform of password encryption scheme (e.g., 8-bit, 10-bit, 16-bit) inconcert with the password protection system to facilitate securecommunication between an external device, such as PC client 102 and theFTP server 131. However, there are drawbacks associated even with theseschemes. For example, a username and password may be encoded as asequence of base-64 characters. For example, the user name Aladdin andpassword open sesame would be combined as Aladdin:open sesame, which isequivalent to QWxhZGRpbjpvcGVuIHN1c2FtZQ== when encoded in base-64.Little effort is required to translate the encoded string back into theuser name and password, and many popular security tools will decode thestrings “on the fly”, so an encrypted connection should always be usedto prevent interception.

In another embodiment, an encrypted connection scheme is used. Inparticular, the FTP server 131 in the IED 110 uses some form of FTPsecurity encryption, such as, for example, FTPS (FTP over SSL), SecureFTP (sometimes referred to as FTP over SSH, i.e., FTP over Secure Shellencryption (SSH)), Simple File Transfer Protocol (SFTP), or SSH filetransfer protocol (SFTP). These FTP security encryption protocolsprovide a level of security unattainable with the previously describedpassword encryption schemes.

FTP over SSH refers to the practice of tunneling a normal FTP sessionover an SSH connection. Because FTP uses multiple TCP connections, it isparticularly difficult to tunnel over SSH. With many SSH clients,attempting to set up a tunnel for the control channel (the initialclient-to-server connection on port 21) will protect only that channel;when data is transferred, the FTP software at either end will set up newTCP connections (data channels) which will bypass the SSH connection,and thus have no confidentiality, integrity protection, etc. If the FTPclient, e.g., PC client 102, is configured to use passive mode and toconnect to a SOCKS server interface that many SSH clients can presentfor tunneling, it is possible to run all the FTP channels over the SSHconnection. Otherwise, it is necessary for the SSH client software tohave specific knowledge of the FTP protocol, and monitor and rewrite FTPcontrol channel messages and autonomously open new forwardings for FTPdata channels.

In further embodiments, the networks may be configured to adhere tovarious cyber security standards to minimize the number of successfulcyber security attacks. The cyber security standards apply to devices,IEDs, computers and computer networks. The objective of cyber securitystandards includes protection of information and property from theft,corruption, or natural disaster, while allowing the information andproperty to remain accessible and productive to its intended users. Theterm cyber security standards means the collective processes andmechanisms by which sensitive and valuable information and services areprotected from publication, tampering or collapse by unauthorizedactivities or untrustworthy individuals and unplanned eventsrespectively. In the various embodiments and implementations of thepresent disclosure, the systems, devices and methods may be configuredto be in accordance with, for example, the Standard of Good Practice(SoGP) as defined by the Information Security Forum, CriticalInfrastructure Protection (CIP) standards as defined by the NorthAmerican Electric Reliability Corporation (NERC), and the ISA-99standard as defined by the International Society for Automation (ISA),the contents of each being incorporated by reference herein. It is to beappreciated that this lists of cyber security standards is merely anexemplary list and is not meant to be exhaustive.

In another embodiment, the IEDs, systems, network topologies and methodsthereof may be employed to implement an enterprise-wide energymanagement reporting, analysis and billing system. As shown in FIG. 10,the system 700 and method of the present disclosure imports historicallog energy usage data from meters, IEDs and other sources 702 andgenerates detailed and useful energy reports for analyzing energy use,planning and load curtailment. In one embodiment, the system 700operates on a client/server architecture, where a server/settings editor704 imports data from various sources 702 enabling at least one client706 to access the data and generate reports therefrom. The system 700and associated methods enable multiple users to generate customizedenergy reports to study energy usage and demand enterprise-wide. Forexample, a user may display Peak Energy Usage for the day, week, andmonth, or compare usage between meters, locations, and customers. Anautomated billing module of the system 700 allows a user to generatesub-metering bills based on customized rate structures for energy andother commodities such as water and gas.

It is to be appreciated that the enterprise-wide energy managementreporting, analysis and billing system of the present disclosure may beimplemented on any of the various network topologies described above, inaddition to other developed or to be developed network topologies.

The system 700 and method (also known as E-Billing EXT system or meterbilling system) integrates three components, with the goal of providingdata collection, analysis, and reporting on metered locations. Toachieve this, it brings in data from data sources, such as meters,analyzes it through the billing software, and stores it in an internaldatabase. The meter billing system and method then also provides theability to retrieve the analyzed data at a later time, and generatereports off that data. From this information, users can then view thelarger picture of the location that meters are recording.

Data is collected and stored in a single place, such as a database.Since the data may include private information and billable data such asenergy usage, it is important that the software provides accountabilityfor any deviation from the original values. Additionally, theconfiguration that affects these values should only be able to bemodified by users which are given the proper permission for thosechanges.

FIG. 11 illustrates a system 1100 for managing scripts, according tovarious implementations of the present disclosure. The system 1100 asshown comprises meters 1102, where each meter is configured to measureparameters of a commodity consumed at a customer location. For example,the meters 1102 may be intelligent electronic devices for measuringelectrical parameters of energy consumption. In other embodiments, themeters 1102 may include any combination of sensing devices for measuringone or more commodities, such as electricity, steam, gas, etc.

The system 1100 further comprises a server 1104 in communication withthe meters 1102 by way of a communication network 1106. The server 1104,for example, may be configured to receive the measured parameters fromthe meters 1102 and store the parameters as log data. The log data maybe stored in a database in direct communication with the server 1104 orlocated remotely in the system 1100 and accessible via the communicationnetwork 1106.

The system 1100 of FIG. 11 also includes a plurality of client devices1108 in communication with the server 1104 by way of the communicationnetwork 1106. The system 1100 also includes a base device 1110 incommunication with the plurality of client devices 1108 by way of thecommunication network 1106. In some embodiments, the base device 1110may be omitted, particularly if the functionality of this device isalready incorporated in the server 1104, one or more of the clientdevices 1108, or other device. The base device 1110 may be a secondserver or another client device. The base device 1110 may be configuredto store one or more scripts or functional chains. Each of thefunctional chains, for example, may comprise software code defining aplurality of functional actions to be performed in a specific sequence.The base device 1110 comprises an interface, such as a network interfaceor user interface, which allows the client devices 1108 to reference thefunctional chain.

According to some embodiments, the base device 1110 may also be a clientdevice, but, in addition to the regular functions of the client devices,may also be configured to enable the other client devices 1108 to callupon the base device 1110 to reference the functional chains stored onthe base device 1110. In other embodiments, the base device 1110 may beconfigured as a second server that supplements the server 1104.

The base device 1110 may supply or execute functional chains for theclient devices 1108 as needed by the client devices 1108. For example,the needs of the client devices 1108 may be based on what the particularclient devices 1108 already store in their memories and what theparticular client devices 1108 need in order to execute variousfunctions related to processing meter information. Any one or more ofthe client devices 1108 that references the base device 1110 for suchneeds may be referred to herein as a “calling device.” Therefore, thecalling device can reference the functional chain from the base device1110 and execute the functional chain.

Many of the embodiments of the present disclosure describe the use ofsoftware applications running on the various devices. For example, theserver 1104, client devices 1108, and base device 1110 may includesoftware applications for executing various functions. However, insteadof the functionality being implemented in software, it should be notedthat the functionality may alternatively be implemented in any suitablecombinations of software, firmware, and/or hardware.

FIG. 12 illustrates an embodiment of a software layout 1250. Thesoftware layout 1250 may be distributed as discussed above with respectto FIG. 11. In other embodiments, the software layout may be containedin one computer system. The software layout 1250 allows multiplesoftware applications to communicate with each other on the samecomputer. As illustrated, the software layout 1250 may include varioussoftware applications, such as log software 1252 (e.g., for loggingmeter data), polling software 1254 (e.g., for polling meters), andconfiguration software 1256 (e.g., for managing configurationinformation of meters).

Additional software applications may include a ScriptManager application1260, a KnownDevices application 1262, and a DeviceScan application1264. The details of these applications are described in more detailbelow. The log software 1252 and ScriptManager application 1260 canstore log information in a device log database 1270. The DeviceScanapplication 1264 is capable of scanning a network, such as network 1106shown in FIG. 11, to execute a discovery process for finding andidentifying meters on the network. As shown as an example, theDeviceScan application 1264 may be able to find at least device 1,device 2, and device 3. The KnownDevices application 1262 is able to usethe information about the discovered meters to supply other applicationswith information about those meters.

Typically, an existing software suite might perform each of a number offunctions of the devices using separate software applications, each ofwhich might be configured separately. Additionally, many of theconfigurations may include manually repeating information which iscommon between them. This may result in a feel of many disjointedsoftware applications, rather than one common tool. Additionally, manyof the tasks that are configured manually may be common ones that arerepeated for every device, such as retrieving logs and configuring theconnections. Repeating these tasks for every device can be timeconsuming, can result in errors, and can be confusing to some users.

The base device 1110 is configured to store a collection of softwareapplication tools which ease the processing and use of meters and meterdata by automating many of the features of the client devices 1108. Somefeatures may include determining the communications parameters of themeters 1102, logging and retrieving data from the meters 1102, andmonitoring the status of those devices.

Additionally, the software application tools may process the meters 1102in a group, rather than as individual devices, which allows for morecomplex concepts to be applied to those devices. For example, some ofthe meters 1102, such as a group of meters at a certain physicallocation, may use the same logging settings. Thus, by gathering thesedevices together in a group, a user could apply those settings to thatgroup of devices with a single action.

One of the features of the collection of software application tools isthe automation of common tasks, such as log retrieval, the generation ofreports, and the detection of meters. One goal of this automation may beto require minimal configuration on the part of the user, so as tosimplify the use of the devices. A second goal of the automation may beto provide a way to perform these actions on a regular basis. It shouldbe noted that other goals may be achieved by the present systems as willbe understood by one of ordinary skill in the art.

Another feature of the suite of software tools includes the ability tobring common components and features of the tools together into a singlelocation (e.g., at the base device 1110). From this location, the clientdevices 1108 may reference the tools as needed. For example, byproviding a common list of devices (e.g., meters 1102) and theirconnection information, the user no longer needs to manually maintainsuch list, but can interface with the device independently.

The system 1100 provides a scripting service or script managementservice, which performs configured actions on triggers. These actionscan include retrieving data from meters, the generation of reports, aswell as performing a common action, such as firmware upgrade, on acollection of devices.

The system 1100 also provides a way to define various parameters of themeters 1102 and stores a collection of device parameters related to themeters in a storage device accessible through the network 1106. Thedevice parameter collection may include, for example, communicationsparameters, device information, and stored data references. Thisinformation can then be used by the other software applications tointeract with the devices in a way that is more meaningful to the user.Additionally, the device parameter collection allows a user on theclient devices 1108 to group devices into “locations,” which allows foractions to be performed upon the devices in the group as one.Additionally, other software applications could use this groupinginformation for various management and reporting purposes. The system1100 also provides a service which scans the network for meters and thenautomatically populates the contents of the device parameter collection.

These three components work together to provide the goal of automationand common device listings. An additional fourth device, referred to asa Launchpad component, is described in more detail below. The Launchpadcomponent provides a front end to the user to provide a common link toall the other components, as well as configuration and status monitoringof the system.

One problem which is often encountered when implementing software thatis composed of multiple functional actions that are meant to worktogether is ensuring that these multiple actions are performed in thecorrect sequence, and at the correct times. In this case, functionalactions are defined as a use of a software component which performs aunique action, distinct from the other uses of the software.Furthermore, a functional action may use or require other functionalactions as input, and its output may be used by other functionalactions. For example, software components may be composed of device logretrieval functional action, a log conversion functional action, and alog viewing functional action. Each of these components performs uniqueactions, but they are required to be used in concert, and in the correctorder, for the user to ultimately view the devices data log. Let such asequence of functional actions be called a Functional Chain, as shown inFIG. 13A. The Functional Chain (FC) in this example includes functionalactions 1 through n.

The problem of coordinating functional actions might be solved bymanaging the interaction of these actions to ensure that each performscorrectly with the other. The drawback of this is that it often requirescode to be rewritten and perhaps redesigned when a new action is added,or existing actions modified in an existing functional chain. Anotherproblem with this approach is that when new software is created thatuses the same or similar functional actions and chains, it may need tobe redesigned and the interaction of these actions may need to beanalyzed and tested again.

One possible solution to the problem of using functional actions inmultiple locations is to implement the actions as interchangeablecomponents, which can be used from those multiple locations with minimumintegration. In this case, an interchangeable component is defined as aset of code or software, which has a predefined interface that allowsmultiple other software applications to use that component withoutredesigning the component. For example, log retrieval could beimplemented as a software component which performs the functional actionof retrieving logs, and defines the interface of specifying the deviceto retrieve from, the logs to retrieve, as well as defining a specificoutput format for the retrieved log. This software component could thenbe used by multiple other software applications to perform the samefunctional action, without requiring the implemented log retrievalsoftware to be changed. As shown in FIG. 13A, one functional action x₁can replace or be replaced by another functional action x₂ in anothersoftware application.

Additionally, so long as the interface between the interchangeablecomponent and the calling software does not change, the interchangeablecomponent could be redesigned without affecting the calling software.For example, the calling software may refer to one or more softwareapplications running on a separate device, such as the client device1108 shown in FIG. 11. Furthermore, a new interchangeable componentwhich performs a similar functional action could be implemented, andused by the calling software with minimum redesign. For example, in thecase of a software component used to retrieve logs from a device, ifanother device existed which defined a different method of retrievinglogs, a new software component could be implemented for this seconddevice, and the calling software would only have to know which componentto use. This interface for using them would stay the same.

This solution can also be configured to include functional chains. Whilethe interfaces between the components are predefined and remain static,the viability of the sequence of actions that compose the chain remainsreliable. Thus an individual component can be changed out in the chain,without requiring the rest of the components in the chain to beredesigned. Furthermore, if the modified component is thoroughly tested,the rest of the chain need not be retested. For example, in the chain oflog retrieval, conversion, and viewing, if the retrieval component hasbeen changed to support a new device, so long as the output of theretrieval is consistent with the previous retrieval component, theentire chain will still work.

Functional chains can be further implemented by applying the same rulesof a functional action to the chain itself. In this case this means thatthe functional chain performs a unique action that can be used inmultiple locations by defining a consistent interface. Then thefunctional chain can be used as an interchangeable component, whichwould allow software to become more modular. For example, a functionalchain could be created that retrieves log data from a meter, and outputsit to a text file in comma separated value format. One softwareapplication could use this chain to retrieve and display a live trendgraph of the historical data. Another software application could usethis chain to retrieve and generate an analysis of the historical data.Another software application could use this chain to keep a localhistory of all the data the device has recorded.

Another problem when implementing functional actions is coordinating thesequence of the actions. This problem is exacerbated when multipleactions are performed in parallel, and their timing is not consistent.An example of parallel actions is illustrated in FIG. 13B, where anumber of sequences N are performed substantially simultaneously. Afirst sequence “A” includes multiple actions, a second sequence “B”include multiple actions, and a third sequence “C” include multipleactions. The first action of sequence B would not be started until thesecond action of sequence A had finished. Sequence C would also stopexecuting at its second action, until the second action of sequence Ahad finished. For example, a functional chain which retrieves andoutputs the logged data from a device could be created, and used onthree different devices, which may take different lengths of time tocomplete. A further action could be used at the end which combines theresults of that retrieval into a single analysis. For that analysis tobe useful, it would be required to wait for all the retrieval chains tocomplete, which would be non-trivial without hard-coding the knowledgeof the completion of the actions.

One possible solution to coordinating actions is to create a specialcomponent which takes as input the functional chains it is to wait on,and has as output a special action which causes later actions to beperformed. Let this special action be called a Completion Trigger. Asshown in FIG. 14, the action “f(T)” is a trigger and is configured toinitiate other actions upon completion. The trigger f(T) initiates thestart of functional chain f(Ra) having n actions and also initiatesfunctional actions f(Rb) and f(Rc). For example, such a specialcomponent could be created that waits for multiple retrievals andconversions to complete, and then executes the action to perform theanalysis.

These completion triggers f(T) could be further implemented by allowingthe calling software to wait for the completion trigger, rather than thecompletion trigger causing the next step in the chain. This would allowthe completion trigger f(T) to be used without requiring any knowledgeabout the software that uses it. For example, in a chain that retrievesmultiple logs that ends in a completion trigger, the calling softwarecould wait for the trigger to raise a notification that it hascompleted, and then process the output files. One possible way toperform this notification could be a TCP message, a kernel semaphore, aWindows Message Event, or other such pushed event notification. Anotherpossible way to perform this notification could be to output a specialfile that indicates that the completion trigger occurred, and thecalling software could monitor for changes. Another possible way toperform this notification, if the completion trigger was contained inanother software application or library call, would be to return from ablocking operation.

Another possible solution is to create a functional chain which containsthe multiple functional chains within it, and performs thesynchronization of them before returning a new output which referencesthe individual outputs. For example, a special chain could be createdfor the purpose of retrieving multiple logs, which outputs a newcomma-separated value (CSV) file that contains the data for all thelogs. As another example, another similar chain could be created, whichoutputs a new file that contains a list of references to the individualretrieval outputs.

Often the use of a functional action does not require knowledge aboutthe output of that action, which may instead be picked up at a latertime. For example, a functional chain could exist which retrieves logdata from a device and may store it in a log database for later viewing.In this case, the use of the chain, such as log retrieval, conversion,and storage, does not require knowing anything about the chain.

One possible implementation of interchangeable components is to abstractthe part of the component that is used in a chain to only the interfacesthat are required by the chain, as shown in FIG. 15. This would allowthe calling software, or caller, to only require a minimum of knowledgeabout the action being performed. For example, for a retrieval andstorage chain implemented as an external application, the usage of thecomponent may only require that the retrieval parameters be passed in,and the success or failure of the action output.

Abstracting interchangeable components could be further implemented bydefining a consistent interface that all components use, regardless ofwhether they encapsulate similar functional actions. This would allowfunctional actions to be used in many different sequences, withoutrequiring refactoring on the part of the components to supportdissimilar actions. In this example, functional chain FC1 includesfunctional actions f(1) and f(2). The actions may be abstracted asneeded to create functional chains FC2 and FC3, where each of FC2 andFC3 would contain all the actions of FC1, such that they could be calledby the same calling device as FC1. A component could exist thatretrieves and stores log data, and another component that sends an emailto a user that an event has occurred. These two components could belinked together, to notify a user when local log has been updated.Another component could exist that polls a device to determine if astate is set, for example if voltage is above a limit, or a new logrecord has been recorded. This component could be linked to the emailcomponent, to notify the user that a condition, such as the exceeding ofa limit, has occurred. In both cases, the email component does not needto know about the previous action.

Many times in software an action is initiated by the user. For example,viewing a polling screen results in the data being retrieved from adevice and presented to the user. As another example, log data isretrieved from a device when the user presses a button. However, thereis often a need for that action to be performed automatically. Forexample, the data on the polling screen may need to be refreshedperiodically. As another example, the log data may be desired to beretrieved whenever there is a new item. Such automation often requiresthat the caller of the action implement the logic for the automation foreach such use.

One possible solution to automation is to create a special functionalaction which performs another action under a configured condition. Letthis be called a Trigger. As illustrated in FIG. 16, trigger f(T) isexecuted to determine if the condition is true. If not, the trigger f(T)is repeated or delayed until the condition is true. When true, thefunctional actions f(1) (and following) are executed. For example, atrigger f(T) could be created which performs an action on an interval,say every 5 minutes. This trigger could be then used along with anothercomponent, which polls device data, and a completion trigger to indicateto a polling screen that fresh data is available to be displayed. Asanother example, a trigger could be created that polls a device, andcompares the value read against a configured setting, such as checkingif the voltage value is above a certain level.

This automation through triggers could be implemented by combining suchtriggers with the functional actions they call, into a single functionalchain. Let such a component that combines both action and triggers becalled a Script. For example, such a script could be created whichperforms a log retrieval process every 15 minutes. In such a case, asshown in FIG. 17, the trigger f(T) would be a timer that checks if theinterval has passed, and the action f(1) would be the log retrieval. Asanother example, such a script could be created that uploads firmware toa device when it is notified that new firmware is available.

One possible implementation of such a script could be to have anexplicit trigger component, and an explicit action component. Such atrigger could then be used to detect if the action should be performed,and if true, the action component executed. Another possibleimplementation of such a script could be to link the trigger to theaction component such that the trigger is executed, and that the triggerexecutes the action component.

Another possible implementation of such a script could be that thetrigger and the action to be executed are both just action components,as shown in FIG. 18. Only a single start point and exit point for thechain of actions would have to be defined. This would allow an arbitrarynumber of triggers f(R1), f(R2), f(R3), etc. and actions f(1), f(2),etc. to be used within the script. Additionally, this would allow forscripts which did not require a trigger, but instead were just used toperform an action.

Automation through triggers could be further implemented by creating acomponent which has the functional action of running other scripts. Letsuch a component be called a Script Runner. In FIG. 19, a script runner,identified as R, is configured to run script “S”. This script runner Rcould then be used by a software component to perform an arbitrary setof actions with only the requirement to setting up the scripts to run,and possibly processing the output. For example, a software componentcould be created that polls various data from a device, flagsindications of device status changes to the user, and displays logevents as they happen. Each of these actions could be implementedthrough a script, and run through the script runner. When any one of theactions completed, the software application would be notified, and theresults presented to the user.

Often actions do not require a specific software component to beinvolved to perform their functionality. The script runner could befurther implemented as a separate software component, as shown in FIG.20, which could then be used to run any such independent scripts,regardless of their source. For example, a script could be used whichretrieves and stores log data for a device on an interval. As anotherexample, a script could be used which monitors the status of a device,and sends an email when the device is no longer accessible. As anotherexample, a script could be used that generates a report at the end ofeach day, such as an analysis of the data from multiple devices. Asingle script runner could be used to run each of these scripts.

Using the script runner as a separate software component may be furtherconfigured to allow it to be run without being started by a user. Onepossible implementation of this could be to run it as a service. Anotherpossible implementation of this could be to check if it is running whenan external software application tries to use it, and automaticallystart it if it is not running.

Scripts could be further implemented by providing the ability to chainscripts and triggers together, as illustrated in FIG. 21. As such, thecompletion of one script leads to the execution of another. For example,an existing script which retrieves and stores logs could be linked toanother script which resets those logs. As another example, an existingscript which polls the status of a device could be linked to anotherscript that sends that information to a server.

One possible implementation of this could be to link multiple scriptstogether with triggers, as shown in FIG. 22A, such that when one script(i.e., S1) completes, its completion trigger calls the next script(i.e., S2) in the chain. Another possible implementation of this couldbe to create a special list of scripts, such that when one is completed,the next is executed, as shown in FIG. 22B.

Linking scripts with triggers could be configured by allowing them totrigger multiple scripts upon completion, as shown in FIG. 23. Asillustrated, the completion of script SB trigger scripts SC1, SC2,through SCn. For example, a script which polls device data could triggera script that displays the value on a UI, as well as trigger a scriptthat stores it in a local data log, as well as trigger a script thatsends an email if the value exceeds some limit.

Linking scripts with triggers could be further implemented by creating atrigger that tests if a condition is true before allowing the script tobe executed, as shown in FIG. 24. Let such a trigger be called a LogicalTrigger (LT). For example, a script which retrieves log data could belinked to a script that generates a report. The report generating scriptcould have a trigger that tests if the log data covers a sufficientperiod of time to generate the report, before doing so. As anotherexample, a script which polls a device's configured time could be linkedto a script that sets the device's configured time. The set time scriptcould have a trigger that compares the device's time against an absolutereference, and only sets the time if it is sufficiently different.

Logical triggers could be configured to determine which of multiplescripts to trigger next, as shown in FIG. 25. This decision couldinclude one script, no script, or a combination of multiple scripts. Inthe illustrated implementation, depending on various conditions, thelogical trigger can trigger script S1 using trigger T₁, trigger scriptS2 using trigger T₂, and/or trigger script S3 using trigger T₃. Forexample, a trigger could be created which monitors multiple qualities ofa device, including but not limited to, readings such as voltage, logstatuses, and device statuses such as system events. If that sametrigger detects new system events, it could execute a script thatretrieves those events for analysis. If that same trigger detects aquality value, such as harmonics or phase angle, exceeding a limit, itcould execute a script that initiates a manual waveform capture, as wellas another script that stores device readings around the time of theevent, as well as another script that retrieves related logs, such aspower quality and waveform logs. If that same trigger detects that it isunable to communicate with the device, it could execute a script thatsends an email to a configured user, to notify them of the problem.

While automating the execution of the script runner supports standalonescripts, there is still a need for functional actions which are starteddirectly by the user, as shown in FIG. 26. For example, the user maywish to see the log data for a device, and that data has not yet beenretrieved from the device. As another example, the user may wish toupdate the firmware of a device. One possible solution to this could beto instantiate a script runner R each time an action is to be performed.Alternatively, just the script S to be executed could be instantiatedeach time an action is to be performed.

Another possible solution to this could be to create a trigger whichexecuted its script when an external decision has been made. Let this becalled a manual trigger. One possible implementation could be to use aninternal flag that the trigger could periodically check. Anotherpossible implementation could be for the script runner to execute thescript directly when the condition has been triggered by the caller. Forexample, the script runner could be implemented such that it could begiven a list of scripts to execute manually, which it then executes,either when it was given them, or on some sort of cycle.

Using manual triggers could be further configured in the case of anexternal script runner, such as the case where the script runner iscontained within its own application, by providing an external mechanismto pass trigger information into the script runner from an externalcaller. Let such an external mechanism be called the Script RunnerInterface.

One possible implementation of such a command mechanism could be toimplement a communication server in the script runner application, whichthe external application could send commands to. For example, a TCP portcould be listened on for commands in a special format, such as binary ortext commands, to initiate the manual triggers. As another example, anhttp server could be used, such that POST messages could be used to sendcommands. As another example, a pipe or message queue could be listenedon for commands.

Another possible implementation of such a command mechanism could be touse a command file, as shown in FIG. 27. For example, an externalapplication 1120 could write a command to a command file 1122, which thescript runner R 1124 would periodically check by reading the contents ofthe command file 1122. As another example, a directory could be usedsuch that each entry in the directory is a command file to execute, andthe script runner would periodically check for new files.

Another possible implementation of such a command mechanism could be touse a database to store a list of commands to execute. For example, theexternal application would insert an entry to the command table, whichthe script runner would periodically check for by reading from thedatabase. Such a database mechanism could be further configured by usinga database server, which would allow for the script runner applicationand the calling application to be on separate computers. For example, asetup could be created where multiple users need to initiate similaractions, such as polling device information, or generating a report,each from a unique remote terminal.

Using a database server as the command mechanism could be furtherimplemented by storing user information from the caller, which thescript runner could then use to verify that the caller is allowed toexecute the script. One possible implementation of this could be tostore a user id in the table along with the command, which could then beverified against a user list containing permissions. Another possibleimplementation could be to use individual command tables for each typeof command, and only give the callers permission to read and write totables that they have permission to execute commands for.

Manually triggered scripts could be further implemented by allowing anyscript to be manually triggered, not just ones which have beenconfigured with a manual trigger. For example, a script could be used toretrieve the logs of a device every 4 hours. If the user wanted to seethe update to date values that script could be manually triggered toinitiate a retrieval and update.

Such commands, as shown in FIG. 28, could be further configured byallowing them to be used for more than just manually triggering scripts.For example, a command could be used to stop a script that is running.As another example, a command could be used to start or stop the scriptrunner itself. As another example, a command could be used to pause thetriggering of all scripts, regardless of if the trigger conditionoccurs. As another example, a command could be used to enable or disablethe triggering of a specific script.

Such commands could be further configured, as shown in FIG. 29, byallowing them to pass additional information to the script runner alongwith the command. For example, a command could be used to add a scriptto be run, and the additional information could be used to describe thescript. As another example, a command could be used to start a script,and the additional information could be used to specify theconfiguration used as input to the script.

Such commands could be further implemented by providing a mechanism toreturn information to the caller. One implementation could be to send aresponse to a command sent via a communications server. Anotherimplementation could be to insert the response information in theoriginal command, such as filling in a field in the database, orappending to the end of a file. The external application could then readthat information out to process the response. Another implementationcould be to store the response as a separate field, such as a separatedatabase table, or a separate file. A unique key from the originalcommand could then be used to link the two.

Using an external mechanism, such as a database, communications server,or file, to communicate between an external application and a scriptrunner application could be further configured to read the currentstatus of the script runner. For example, the startup time of the scriptrunner could be queried. As another example, the list of running scriptscould be queried. As another example, the details and configuration of ascript could be queried.

One possible implementation of this is shown in FIG. 30. In this case,the script runner 1140 writes or updates its current status to a scriptrunner interface 1142 periodically, which the external interface 1144could periodically read. Another possible implementation could be toprovide a command (e.g., initiate update) that the external application1144 could send that would cause the script runner 1140 to update itscurrent status. The external application 1144 could then read thatupdated status from the script runner interface 1142, or it could bereturned as the result of the command. Also, the script runner interface1142 may store status information in storage device 1146.

Such a status mechanism could be further implemented by restricting whatusers were allowed to read which statuses. One possible implementationof this, as shown in FIG. 31, could be to provide a user ID table 1150that stores users, IDs, along with status commands, which could then beverified against a user list containing permissions. In response to aquery from an external interface 1152, the script runner 1154 canretrieve the status information from the user ID table 1150 and providethe status to the requesting external interface 1152. Another possibleimplementation could be to use individual status tables for each type ofstatus, and only give the callers permission to read from tables thatthey have permission for.

Such a status mechanism could be further implemented by also logging theactions that the script runner takes, as shown in FIG. 32. For example,the script runner 1160 while running scripts S1, S2, etc. can record thefunctional actions and the times that each script was run in an actionlog 1162. As another example, the input and output from a script couldbe recorded in the action log 1162. One possible implementation of sucha log could be to store each action as an entry in a database table.Another possible implementation of such a log could be to store eachentry in a log file. Such a log file could store each entry in manyways, including on a line as text, as html entries, as xml formattednodes, or as binary records separated by a special character.

As shown in FIGS. 33A-33C, such a log could be further implemented byalso storing error information. For example, an error may be identifiedif a script failed to start due to a bad configuration. As anotherexample, if a script returned an error code indicating that it had aproblem. As another example, if the script runner detected a problemwith itself or its interface, such as corruption in the database orcommand file directories. As another example, if the script runnerdetected that an external application was trying to execute commandsthat it did not have permission for. The script runner R can store theerrors in error log 1166.

Such a log, or another log, could be further implemented by also storinginformation from the scripts themselves, such as the actions they took(e.g., action log 1162 shown in FIG. 32), the errors they encountered(e.g., error log 1166), and the values they detected (e.g., value log1168). For example, a script which retrieves logs could report that itwas querying the log header information, the values that werediscovered, the actions performed to retrieve the log, and any errorswhich occurred during the retrieval.

So many log entries could quickly become confusing to anyone trying tounderstand what happened. One possible solution to this could be to linkall the log entries which occurred during a single run of a chain ofscripts with a key. One possible implementation of this could be to keepa list of each time a script was started, such that the key could thenuse the index of this list. Another possible implementation of thiscould be to use a similar list, but to generate a unique id, such as aGUID or hash, and store it in the list. This unique ID could then beused as the key. Another possible implementation could be to use a keygenerated from the first log entry, such as its unique index.

Another possible solution could be for each log entry for a chain ofscripts to refer back to the previous entry, all the way to thebeginning of the chain. Another possible solution could be to store eachscript chain individually. For example, all the entries for a singlescript chain could be logged to a single file. As another example, allthe entries for a single script chain could be logged to a single table.

Such a command and query interface, as mentioned above with respect toFIGS. 26-31, could be further configured by providing a library orapplication programming interface (API) which callers could use to sendand receive data from the interface. This would allow the software codeto be written without requiring including details of the specificmechanism of the interface. This would also allow the interface code,which may be common among the software applications, to not have to berepeated in multiple locations, thus reducing complexity. For example, asoftware application could send a manual start command with thefollowing code snippet: cmdapi.SendCmd(“START”, script_id). The softwarewould not have to know if the interface was a database, a file, or acommunications server. One possible implementation of such an API couldbe to provide a library code base, such as a dynamically loaded library(DLL), a statically linked library, a plug-in, or common source code.

Another possible implementation of such an API could be to provideanother software component, which is called to perform the commands andqueries. For example, a command-line application could be used to send acommand by invoking the command-line application with the command as anargument. As another example, a command-line application could be usedto perform a query by invoking the command-line application with thequery parameters as arguments, and the results could be written to afile, or standard out, and read by the caller.

Script Chains could be further implemented by using an interpretedsequence of actions. Such an implementation would allow for easycreation of an arbitrary sequence of triggers and actions. For example,it could be implemented using an interpreted language, such as but notlimited to Perl, Python, Lua, JavaScript, or one created for thepurpose. As another example, it could also be implemented as acollection of action objects, which are then linked together through theinterpreted sequence. Such an interpreted sequence could be a text filewith each action or trigger to perform on a line, with each componentconfiguration specified on that line.

Such an interpreted sequence could be further configured for providing agraphical interface to represent such a sequence, as shown in FIGS. 34and 35. One possible representation could be to show each action andtrigger as a square or other such shape, and show how each componentcalls the next as an arrow or other such link, as shown in FIG. 34.Actions and triggers could also be represented by icons or images. Sucha representation could also use different shapes or images to representdifferent types of actions and triggers. In such a representation,information about the component, such as configurations, could berepresented as text inside the shape. Such a representation could alsoautomatically arrange the actions and links to better represent the flowof actions. For example, the first action could be placed at the top orleft, and each sequential action arranged below or to the right of theprevious.

Another possible representation could be to display the sequence ofactions and triggers as lines in a grid, where the sequence of actionsis represented vertically. Another possible representation could be todisplay the actions and triggers as nodes in a tree, as shown in FIG.35, where each called component is represented as a child of the callingcomponent.

Such an interface could be further implemented by allowing the sequencesto be designed on the interface. One possible implementation of such adesigner could be to allow a shape representing a specific type ofaction to be placed on a field that contains the graphicalrepresentation of the script. This action could then be linked to otheractions by dragging a link representation to another action. This actioncould also be linked to other actions by manually selecting the actionit is to call from a list.

Another possible implementation of such a designer could be to allow anaction or trigger to be inserted after another action or trigger byclicking a button. The relation between the calling action and thecalled action could be determined by the button pressed. Another buttoncould be used to change the relation between actions, such as movingthem up or down in a grid, or to a different level in a tree.

Such an interface could be further implemented by graphicallyrepresenting the actual progress of the script as it executes. Forexample, the current component being executed could be represented by acolor change. As another example, the current component being executedcould be represented by a selection marker, such as a border or a halo.As another example, the current component being executed could berepresented by a change in its shape, image, or location.

Representing an executing script graphically could be further configuredfor action chains by representing the history of the actions. Forexample, if one of multiple actions was taken, the actions not performedcould be represented by a color change, such as dimming, graying themout, making them transparent or translucent, or temporarily hiding them.As another example, if one of multiple actions was taken, the linkrepresentation between the caller and called action could behighlighted, such as changing the color, size, style, or giving it ahalo.

Representing an executing script graphically could be furtherimplemented by displaying the input and output to each action ortrigger. One possible representation could be to display the input andoutput as text. For example, a popup shape could be displayed near theaction or trigger, in which the text could be displayed. Furthermore, aline could be used to denote the connection to the user. As anotherexample, a section of the representation of the action or trigger, suchas a field in a grid, a child node in a tree, or a section of the shape,could be used to display the input and output. Another possiblerepresentation could be to display the input and output using images todenote what kind of input they represent.

Representing an executing script graphically could be furtherimplemented by displaying the action log along with the actions andtriggers. For example, a scrolling list could be displayed that showseach log entry as it occurs. As another example, a text field could showthe last log entry or the current state of the action or trigger.

Representing an executing script graphically could be furtherimplemented by indicating when errors occur. For example, therepresentation of the action or trigger could change color, such as turnred, to indicate that it encountered an error. As another example, anerror icon, such as an exclamation mark, could be displayed near theaction or trigger. As another example, a popup shape could be displayedthat contains the error message. As another example, a text field couldshow the last error message.

While a standalone Script Runner software component that was written fora specific set of actions can be used, a generic standalone scriptrunner software component that allows for running arbitrary scriptswould be more useful. However, since the script runner's knowledge ofthe scripts must be minimal, it is difficult to properly construct thescript objects to be used by the script runner.

One possible solution to such generic scripts could be to provide a wayfor the calling software to define the scripts to be executed. Onepossible implementation of this could be to pass the script in throughthe script runners command interface, such as a command database orcommunications server. Such an interface would require that a transferformat for the script be defined, which allows the script to betransferred between two applications, and reconstructed at the otherside. For example, scripts could be represented as an interpreted textfile. As another example, scripts could be represented as XML nodes. Asanother example, scripts could be represented as a binary structure.

Such an interface could be used by the calling software to initializethe list of scripts that it requires. For example, when the callingsoftware is being initialized, it could query the list of all scripts,and load the scripts that it needs. Finally, when the calling softwareshuts down, it could remove the scripts it no longer uses. As anotherexample, the calling software could query if a script was loaded everytime it wanted to use that script, and load it if necessary.

Another possible solution to such generic scripts could be to store thescripts to execute separately from the script runner, such that theycould be configured while the script runner was not running, andindependently of any particular calling software. One possibleimplementation of this could be to store each script as a file, whichcould be loaded when the script runner starts up. Such an implementationwould require that a storage format for the script be defined, whichallows the script to be configured, stored in a file, and reconstructedat a later date. For example, scripts could be represented as aninterpreted text file. As another example, scripts could be representedas xml nodes. As another example, scripts could be represented as abinary structure.

Another possible implementation of storing the scripts could be to storethem as entries in a database, which could be loaded when the scriptrunner starts up. Such an implementation would require that a storageformat for the script be defined, which allows the script to beconfigured, stored in a database field, and reconstructed at a laterdate. For example, scripts could be represented as an interpreted textentry. As another example, scripts could be represented as xml nodes. Asanother example, scripts could be represented as a binary structure. Asanother example, a database table could be defined which represents eachaction as an enumerator, and uses other fields for customization.

Storing scripts separate from a software application would require a wayto store the configuration for those scripts. One possibleimplementation could be to store the configuration as part of the scriptdescription. Another possible implementation could be to store theconfiguration separate from the script, such as in a separate databasefield or table, or a separate file.

Storing scripts separate from a software application would require a wayto configure those scripts. One possible solution could be to providecustom software whose purpose is to initialize those scripts. Anotherpossible solution could be for the calling software to initialize thescripts they need the first time they are run. Another possible solutioncould be to provide a software component that could be used to configurethe scripts.

Using a configuration software component could be configured by allowingthe user to configure the associated scripts. For example, the usercould decide that they want to be notified if a device resets. Theycould configure a script that triggers when the last reset time changes,and sends an email with a notification. Such a script could then bestored for the script runner to use. As another example, the user couldconfigure a script to retrieve the devices logs every hour.

FIG. 36 illustrates an example of a configuration software componentthat allows a user to configured scripts. As shown in this embodiment, aportion of a front end user interface 1190 enables a user to select oneor more “Actions to be Taken”, select “Which Meters” the actions applyto, “When” the action is to take place, the “Conditions” of execution ofthe actions, and “What to do with Outputs.” Therefore, the frontend 1190enables the user to create a script using a simple format.

While generic scripts can be very flexible and useful, they can alsorequire a significant amount of time and knowledge to properlyconfigure. One possible solution to simplify configuration by the useris to provide specific configuration frontends to the user, such thatthey only need to enter information pertinent to the action they wantperformed. For example, log retrieval could be implemented as a scriptthat calls an external tool with a set of command line parameters thatindicate the details of what logs to retrieve, the time range, where tooutput the results, and the device to retrieve from. Constructing such acommand line would probably be beyond the skill of most users. A scriptconfiguration interface could be created that is tailored specificallyfor log retrieval, where the user only has to pick the device toretrieve from, and the logs they want to retrieve. The softwarecomponent could determine the rest of the values, and construct thescript appropriately.

Another possible solution to simplifying configuration is to providescript templates, which are scripts that perform common actions, andrequire minimal configuration on the user. For example, a script whichperiodically checks if a devices firmware is up to date, and updates thefirmware if not, could only require the user to specify the device tocheck.

Script templates could be implemented by creating such scripts thatperform their actions on a collection, such as a list of devices, andthus the user need only enable or disable the script. For example, ascript could be created that monitors a device for resets, and sends anemail on its occurrence. Such a script could be modified to perform thecheck on every device in a list, which could be edited by the user, orfilled from another source.

Simplifying configuration could be further implemented by providing away to specify a configuration that is filled in when the script is run.For example, a script that was performed on a list of devices could getthat list when the script is executed; the next time that script wasrun, the list may be different, and the script would use that new list.As another example, a script may write to a log file, where the name ofthe file is the time that the script was performed.

One possible implementation of such dynamic configurations could foreach script to have unique configuration fields that describe how theconfiguration should be used. For example, a script which writes a filecould have a configuration field that specifies how the filename is tobe generated. This field could contain values such as, but not limitedto, use a specific filename, to use a timestamp, to use a location name,or to use a device name. As another example, a script which retrieveslogs from a device could have a configuration field that specifies whereto get the device to use. This field could contain values such as, butnot limited to, use a specific device, use a file that contains a listof devices, or query the list of devices from another softwareapplication.

Another possible implementation of such dynamic configurations could befor configurations represented as text to contain special replacementtags. Such a tag would then be replaced by the software component whenthe script runs to determine the specifics of the configuration at thattime. For example, in a script that writes to a file could use a tagsuch as “<TIME.CURRENT>”, which would insert the current time in afilename such as “logs\<TIME.CURRENT>.txt”. As another example, a tagsuch as “<LOGS.DIR>” could be used to dynamically specify the locationof the log directory. As another example, “<DEVICE.CONNSTR>” could beused to specify a connection string for the device that the script isusing.

Dynamic configuration could be further implemented by providing amechanism to enumerate a list, and to apply the configuration andscripts they describe, to each item in the list. For example, a list ofdevices could be provided such that the script is performed on each itemin the list, but the configuration of the script only describes onedevice. As another example, a script which retrieves logs from a devicecould enumerate over a list of logs to be retrieved.

One possible implementation of this could be to provide a list of thingsfor the script to enumerate over, and use replacement tags in theconfiguration to specify details to use from each item enumerated. Thescript would then be implemented to process this list specially, andperform its actions on each item. For example, in a script whichenumerates over a list of devices, the tag “<DEVICE.NAME>” could be usedto specify the name of the device currently being processed. As anotherexample, in a script which enumerates over a list of logs, the tag“<LOG.ID>” could be used to specify the log currently being processed.

The list to enumerate could be implemented by allowing it to bespecified using a filter. For example, in a list of devices, a filtercould be used to specify that only devices which support log retrievalshould be enumerated. As another example, in a list of log data, afilter could be used to specify that only channels which contain data ina specified time range should be enumerated. This filter could beimplemented in many ways, including but not limited to wildcards andregular expressions.

Configuring scripts separate from the script runner could be furtherimplemented by providing a way for the script runner to refresh whenscripts have been added or changed. For example, if the script runner iscurrently running, and a new script is added, it could update thescripts it is executing. As another example, if a script is changedwhile it is being executed, it could defer the update of the script tillit was completed, then perform the update.

One possible implementation of this refresh could be for the scriptrunner to check the script configuration periodically, and if it seesdifferences, to load those changes. For example, when it finishes withan executing script. As another example, it could check to refresh on aninterval. Another possible implementation of this refresh could be forthe command interface to provide a refresh command, which would indicateto the script runner that it refresh its scripts.

Systems for providing meter information are further described inaccordance with various embodiments disclosed in the present disclosure.For example, FIG. 37 illustrates a system 1200 that is configured toallow access to meter information and parameters. As shown, the system1200 comprises a plurality of meters 1202, a server 1204, a plurality ofclient devices 1208, and a storage device 1212. Each of the meters 1202is configured to measure parameters of a commodity consumed at acustomer location. The server 1204 is configured to operate incommunication with the meters 1204 by way of a network 1206. The server1204 is configured to receive the measured parameters from the meters1202 and store these parameters. For example, the measured parameter maybe stored in the storage device 1212. The client devices 1208 are alsoconfigured in communication with the server 1204 by way of the network1206. At least one of client devices may be considered to be a callingdevice. The storage device 1212 is able to communicate with theplurality of client devices 1208 by way of the network 1206. The storagedevice 1212 may be configured to store meter information related to themeters 1202. The meter information includes at least connectioninformation to be used to enable the one or more calling devices toaccess the meters 1202 as needed. Furthermore, the one or more callingdevices are configured to reference the storage device 1212 to inquireabout one or more meters 1202 and to receive the meter informationrelated to the one or more meters.

When dealing with communications oriented devices, such as meters, it iscommon to conceptually organize those devices by their connection, asthat is typically the first parameter that must be dealt with to use thedevice. However, as this device is used, the relevance of thatconnection diminishes, which may lead to confusion on the user's part asto what device they are dealing with. Additionally, in today's connectedenvironment, it is common for connections to frequently change, whichoften requires extensive reconfiguration of many software applications.For example, some USB devices change their connection information everytime they are plugged into a different USB port. As another example,when devices are on a network and configured to get their address fromDHCP, those addresses may change every time the devices start up.

One possible solution to this could be to store connection informationfor a device in a single place, such as in the storage device 1212. Areference to that common device (e.g., storage device 1212) may be usedin each of the software applications running on the client devices 1208.Let such a usage of a device reference be called a Known Device 3900, asshown in FIG. 39. When a software application 3902 wants to use theconnection for that device, it can look up the current connection list3904 using the device reference key 3906. This would allow softwareapplications to always use the most up to date connection withoutextensive reconfiguration. Additionally, this would allow users toconceptualize devices by what they do, rather than how to connect tothem.

For example, a software component which displays the current readings ofa device could allow the user to select which device to view from a listof devices. Once selected, the software component would then perform allcommunications using the stored connection settings for that device. Ifthe connection settings for that device changed, the polling softwarewould not be required to know about that change; only the storedconnection information would have to be changed.

As another example, a software component which retrieves logs from adevice could be configured to use the device reference instead of theconnection information. Alternatively, for such a software applicationthat only accepted connection information, such as a URL in a webbrowser, a second software application could generate that connectioninformation from the stored device information, and pass it to the firstsoftware application. As another example, if three such softwareapplications were used, all referencing the same device, there would beno ambiguity as to whether they were all interacting with the samedevice, as there would be if connection information had to be entered ineach one.

One possible implementation of storing known devices could be toconfigure the storage device 1212 as a database which stores a list ofsuch known devices, along with their connection information. Anotherpossible implementation could be to store such a list in the storagedevice 1212 as paired entries in a text file. Another possibleimplementation could be to store a file for each device in a directoryin the storage device 1212, where the connection information is an entryin that file.

Storing the connections for known devices could be implemented byallowing multiple connections to be stored. For example, a device (i.e.,meter 1202) may have multiple communications ports, such as a networkconnection, a serial connection, and a USB connection. The user on theclient device 1208 (or calling device) could then be presented with alist of which connection to use. One possible implementation of thiscould be to store the device list separate from the connection list, andallow the connection in the connection list to reference back to thedevice it applies to. Another possible implementation could be toorganize the stored known devices in a tree hierarchy, such as an XMLfile, or a file for each device, and store the list of connectionsthere.

Storing multiple connections for a known device could be implemented bydesignating one connection as a primary connection, such that it wouldbe the connection used when no other specific type of connection wasspecified. For example, in the case of a device having a serialconnection and a network connection, the network connection could bespecified as the primary connection, such that it is used unless anotherconnection is explicitly specified.

Storing multiple connections for a known device could be furtherimplemented by storing information about that connection, such that itcan be used by the user or software application to determine the bestconnection to use. For example, a name could be assigned to eachconnection to indicate to the user which connection is which. As anotherexample, a measured throughput or communications speed could be stored,and used to determine the fastest connection for log retrieval purposes.As another example, the type of the connection, such as serial ornetwork, could be stored. This information could then be used todetermine which connection to use if the network interface on thecomputer was down.

Storing multiple connections for a known device could be furtherimplemented by automatically trying each connection if the previous onefails. For example, if a device has a wired network connection, awireless network connection, and a cellular data connection, if thecellular data connection dropped, the wireless connection could then betried. If that then failed, the wired connection could then be tried.

Storing multiple connections for a known device could be furtherimplemented by using multiple such connections in parallel. For example,in a device which has two serial connections, one connection could beused for polling, while the other was used for log retrieval. As anotherexample, as serial connections can only be used by one softwarecomponent at a time, a second such connection could be used if the firsthas already been locked by another software component.

Storing connections for a known device could be further implemented bystoring a “last used time” parameter. For example, this time could beused by the user to determine how active a connection is. As anotherexample, with multiple connections, this time could be used to determinewhich should be tried first.

Storing known devices could be implemented by making the list accessiblefrom multiple locations. For example, the known connections could bestored in a database server, which multiple computers could connect to.As another example, the known connections could be stored in a file orfiles accessible from a networked or shared drive. As another example, asoftware component could be created that propagates changes to the knowndevice list between computers. As another example, the known device listcould be stored on a portable device, such as a hard drive, compactflash disk, SD card, USB storage, CD, or other such media. It could thenbe used on multiple computers by moving the files around.

Making the known device list more accessible could be furtherimplemented by allowing devices to be imported and exported from thelist. For example, a portable list, such as on a CD, could be importedto a local known devices list. As another example, the devices from alist could be exported and then emailed to another user.

One possible implementation of exporting could be to create a secondcopy of the known device list by enumerating each entry in the sourcelist, and writing it to the destination list. Another possibleimplementation of exporting could be to make a copy of the source file.Another possible implementation of exporting could be to convert eachsource entry to another format, such as text or XML, so that it would beeasier to transfer.

One possible implementation of importing could be to enumerate eachentry in the source list, and insert it to the destination. If aconflict was found, such as a device that already exists, or aconnection that conflicts with other existing connections, the usercould be notified and asked for a resolution.

Storing known devices could be further implemented by also storinginformation other than connections about each. This could be used by asoftware application to make decisions about the device without havingto connect to it. This could also be displayed to the user, to betterunderstand the devices they are looking at. For example, the firmwareversions of the device could be stored 3908, as shown in FIG. 39. Asanother example, settings for the device, such as but not limited tohookup, serial number, calibration, and log settings, could be stored.As another example, a display name could be assigned to the device,which could then be shown on UI's when the device is being displayed. Asanother example, a unique identifying name could be assigned to thedevice, which could then be used to reference the device separate fromother devices. As another example, the last time the device was known tohave reset. As another example, the last time the device settings werechanged. As another example, the last time the firmware was changed.

Storing information about a device could be implemented by storing adevice type, which would uniquely identify it from other types ofdevices. For example, this could be used to group the device with otherlike devices. As another example, some devices of like type storeinformation in similar locations. This could be used to determine whichlocation to use to retrieve that information. As another example, thedevice type could be used as a filter to only show specific, or not showspecific, types of devices.

Storing information about a device could be further implemented bystoring features that are supported by the device. These could then beused by software to determine what features to display to the user.These could also be used by software to determine how to perform featurespecific actions. For example, if multiple devices supported differentmethods of log retrieval, the supported features could be used todetermine which method to use. As another example, if a device supportedmultiple communications protocols, the supported features could be usedto determine which protocols to use, or to display as options to theuser.

Storing information about a device could be further implemented bystoring application information relevant to the device. For example, thelocation that the retrieved log data for a device could be stored. Thislocation could then be used by the retrieval software, the analysissoftware, and the data view software.

Storing information about a device could be further implemented bystoring extra information entered by the user. For example, the usercould describe the physical location of the device. As another example,the user could enter notes such as but not limited to, installationtime, last service date, or notes on wiring. As another example, theuser could store an image to be shown in relation to that device, whichcould then be displayed by the software application.

Storing information about a device could be further implemented bystoring security information for the device. For example, a device mayrequire login information to retrieve logs. The stored login informationcould be used by a log retrieval software component. As another example,a device may require login information to read certain values, such asenergy. The stored login information could be used by a polling softwarecomponent. As another example, the user could store login information sothey do not need to enter it every time they perform a secure action,such as retrieving logs, updating firmware, or updating settings.

As much of the information stored about a device could be consideredsensitive, such as security info, storing information about a devicecould be implemented by only allowing authorized software applicationsto access that information.

One possible implementation of securing sensitive entries could be toencrypt each field with an encryption algorithm, such as but not limitedto AES or Blowfish encryption. For example, the login information couldbe encrypted so that only log retrieval software could use it. Anotherpossible implementation could be to encrypt the entire contents of theknown device entry.

Encrypting each field could be implemented by using a different key foreach field, or groups of fields, such that a software application onlyhas to be given permission for the entries it needs. For example, logretrieval software may have the key for connection information, devicefeatures, and login information, but not location information. Asanother example, a polling software component may not need access tologin information.

Another possible implementation of securing sensitive entries could beto lock the contents such that only users with appropriate permissionscould access the information. For example, a database or other suchfile, which supports user permissions, could lock access to the deviceinformation only to authorized users. As another example, read access tothe physical file that holds that information could be restricted onlyto software running under certain users.

Storing information about a device could be further implemented by theinformation being updated by the software as they gather the informationfrom the device. For example, when a user connects to a device withoutusing the known devices, that connection could be added to the knowndevices. As another example, when a software application connects to adevice, it could poll the device information such as serial number,description, device type, and firmware versions, and store them to theknown devices. As another example, when the user enters logininformation to perform a secure action, such as retrieving logs,updating firmware, or updating settings, they could be given the optionto store that login information for later use.

Storing information about a device could be further implemented bystoring when that value was changed. For example, the time the firmwarewas updated could be stored, even if the firmware was not changed atthat computer. As another example, the time a setting, such as devicename, was changed could be stored.

Storing information about a device could be further implemented bykeeping a history of the information, using the newest for the currentvalue. For example, the history of firmware versions of a device couldbe used to track bugs and errors in the device. As another example, thehistory of settings in a device could be used to decide which settingsto apply to log data that has been previously retrieved.

Storing information about a device could be further implemented bykeeping a history of the actions that each software component takes onthat device. For example, a software component could log each time itretrieves logs from the device. As another example, a software componentcould log each time it reset the energy, which could then be used byanalysis software to determine if the logged energy values areincreasing properly. As another example, a software component could logeach time it changes the firmware of the device. As another example, asoftware component could log changes to the programmable settings. Asanother example, a software component could log each time it resets thelogs.

Querying device information could be implemented by creating anidentification library, which provides a common interface for queryingthe features of a device. For example, the library could contain afunction QueryDeviceType( ) which would attempt to identify which devicewas being used, what features it supports, and how to interact with it.As another example, using the device type and features, a functionQuerySerial( ) could be implemented, which handles getting the serialnumber, regardless of the device type. Such a library would simplify theimplementation of both storing information about a device, and thesoftware that performs the query of that information.

Such a device library could be implemented by using a configurationfile, which allows devices to be defined without changing the library.For example, when a new device is defined, a descriptor entry could beadded which defines the device identification string, what features itsupports, and which of the known methods of retrieving deviceinformation it supports. Such a descriptor could then be referenced whendetermining the device type.

Many software applications are written with a single device at a time inmind. For example, a configuration software application may allow theuser to configure the settings for a single device, but to configureanother device requires switching to that other device, and performingthe configuration again. As another example, a polling softwareapplication may display readings for a single device, but to compareagainst another device may require disconnecting and reconnecting to thesecond device, or opening a second copy of the software application.

However, in many instances a collection of such devices may be requiredto fully describe the role they play. For example, multiple electricalmeters may be installed in a building, one for each room. To properlydescribe the electrical qualities of that building, such as voltagelevels, power quality, and energy usage, it makes more sense to view allsuch devices together.

One possible solution to this is to group devices together intoLocations, such that software applications could be aware of, andpresent, all such devices together. For example, a polling softwareapplication could display the readings of each meter in a building inparallel, and furthermore, display a summary of their values. As anotherexample, a software application which resets a meter's energy valuescould perform the reset on all the devices at a location together, suchthat they remain in sync. As another example, the timestamps of alldevices at a location could be updated together. As another example, ananalysis software application could display the sequence of eventsbetween multiple meters during an event, such a surge moving along apower line, or the connection between toggling a relay and the voltagelevels.

One possible implementation of this could be to store a list of eachdevice at a location. For example, a file could be created for eachlocation, listing each device to be included. As another example, thedevice list could be stored in a database, using a foreign key toreference the location they belong to. As another example, an XML filecould be used to store each location, and to store the device list ineach location.

Another possible implementation could be for each device to referenceeach of the other devices in its group. For example, the storage of thedevice in the known devices list could contain a reference, such as aforeign key or a key name, to the location it belongs to. As anotherexample, each device could contain a list of the key for each of theother devices that belong to its group.

Storing devices in groups could be implemented by allowing locations tocontain groups of other locations. For example, a multistory buildingmay be considered location “A”, and each floor a location within thatgroup “A”. Each floor location could then be broken into individuallocations for each room, in which a group of devices for that room couldbe kept. In addition, each of those locations may have devices inaddition to their sub locations. For example, each floor location mayhave a common meter used to measure the electrical usage of the entirefloor. Such a device would be grouped with the floor location.

Storing devices in groups could be further implemented by allowing adevice to be contained in multiple locations. For example, a meter maymeasure electrical usage, as well as count pulses from a steam counter.In such a case, the electrical usage may be desired to be groupedseparately from the steam usage. As another example, a meter may havemultiple current inputs, allowing it to be used to measure theelectrical usage across multiple rooms on a floor. Each of theseindividual usages could be grouped separately.

Storing devices in groups could be further implemented by also storinginformation about each location, which could be further used by thesoftware for analysis and reporting. For example, square footage of alocation could be stored, and then used as a comparison metric whengenerating a usage report. As another example, the number of occupantsof a location could be stored.

Storing information for a location could be implemented by allowing alog of such values to be stored. For example, a trend of the averagetemperature for each day at that location could be stored. Thistemperature trend could then be used to analyze the electrical usage forthat location. As another example, the number of customers daily at aconsumer location, such as a store, could be logged and later displayedas a trend.

Storing information for a location could be further implemented byallowing formulas to be stored, such that a new value could be speciallydefined for that location. For example, a location may have multiplesub-locations, all of which feed off a central electrical line. Aformula could be defined to create a usage value which is the centralusage, minus the sum of the sub-locations, describing the usage of justthe common area.

One possible implementation for storing information about a locationcould be to store it as an entry in the location storage, such as a fileor database. Another possible implementation could be to store it as aseparate file, which is referenced by the location storage. Anotherpossible implementation could be to create a special device which isused to describe and log data about the location. Such a special devicewould have all the qualities previously described for known devices.

Grouping devices into locations could be further implemented byproviding a library or application programming interface (API) whichcallers could use to query or manipulate the contents of the list. Thiswould allow the software to be written without requiring includingdetails of the specific mechanism of storing the locations. This wouldalso allow the query and manipulation code, which would be commonbetween software applications, to not be repeated in multiple locations,which reduces complexity. For example, a software application couldgroup three devices by just creating a list of those devices, andcalling the following code snippet:locationapi.CreateGroup(“locationname”, devicelist). The softwareapplication would not have to know how the location group was stored.

One possible implementation of such an API could be to provide a librarycode base, such as a dynamically loaded library (DLL), a staticallylinked library, a plug-in, or common source code.

Another possible implementation of such an API could be to provideanother software application, which is called to perform the queries andmanipulations of the groups. For example, a command line applicationcould be used to create a group by invoking the command line applicationwith the location name, and list of devices to group, as arguments. Asanother example, a command line application could be used to perform aquery by invoking the command line application with the query parametersas arguments, and the results could be written to a file, or standardout, and read by the caller.

Such an API could be further implemented by providing the ability togenerate lists and reports of the locations and devices. For example, itcould be used to generate a webpage which contained a list of eachlocation, and links to connect to each of the devices at that location.As another example, it could be used to generate a report of thesettings for each device at a specified location.

One problem commonly encountered when dealing with connection orienteddevices is finding the parameters for that connection. For example, witha serial device, one must first figure out what communication port thedevice is attached to. Next, the baud rate, parity, protocol, address,and other configurations must be determined. As another example, with anetwork device, the IP address must be determined, which in the case ofDHCP or dynamically assigned address rules, may not be a fixed address.

This problem is compounded when those parameters can change over time.For example, with USB to serial converters, often the com port changeseach time they are plugged into a computer. As another example, withDHCP assigned network addresses, the IP address may change arbitrarilyas the DHCP lease is renewed.

According to some embodiments of the present disclosure, systems areprovided for overcoming these issues by managing parameters related tometer connections as described below. As illustrated in the embodimentof FIG. 38, a system 1300 that manages meter connection parameterscomprises a plurality of meters 1302. Each meter is configured tomeasure commodity data representing at least one commodity beingconsumed at a location. The system 1300 also includes a server 1304 incommunication with the meters via a network 1306. The server 1304 may beconfigured to receive and store the measured commodity data from themeters 1302. Also, the server 1304 is further configured to obtain meterconnection parameters related to the meters 1302. The system furthercomprises a storage device 1312 in communication with the server 1304via the network 1306. The storage device 1312 is configured to receivethe meter connection parameters from the server 1304 and store the meterconnection parameters. The meter connection parameters, for example,enable a client device 1308 connected to the network 1306 to identify atleast one meter and communicate with the at least one meter.

One possible solution to finding communications parameters could be toprovide a mechanism by which the device could be identified regardlessof the address change. One possible implementation of this could be todesign a USB to serial adapter such that it provides a unique identifierin addition to performing the serial conversion. This unique ID couldthen be used by a software application to detect each device uniquely,and assign the use of the associated com port to the device.

Another possible implementation could be to detect the addition of a USBdevice to the computer, and if it was a serial to USB converter, attemptto determine if a known device is connected to it. For example, whensuch an event was detected, a software application could send a request,such as a Modbus RTU message, to detect the device.

Another possible implementation could be to use a known MAC address,which is uniquely assigned to each network device, and send customcrafted network messages directly to that MAC address. If the device wason the same subnet as the requestor, it would then respond and aconnection could be established. This could be further implemented byresponding with the IP address that the device was configured to, whichcould then be used by the requestor for standard network communications.

Another possible implementation could be to use a known IP address andMAC combination, which would not conflict with any known device, such asa broadcast address. This message could then be sent to all listeningdevices using a protocol such as UDP or UPnP, which could then respondwith an acknowledgment of their existence, along with theircommunications parameters.

Another possible implementation could be for the device to registeritself with a common server, such as server 1304 or other server, whichcould then be used by a software application to determine the properaddress to use, as shown in FIG. 40. For example, when a network device,e.g., meters 4002, received a new IP address, it could register thataddress with a common server, e.g., server 4004, which would be at afixed known address. Such a fixed address could be a fixed ipv4 address,a fixed ipv6, or a fixed URL, which would allow dynamic redirection toan arbitrary server through a DNS. As another example, the device 4002could broadcast the new address, which the common server could listenfor, thus not requiring that a fixed known address be used.

Using a common register server could be implemented by allowing eachdevice to also perform this registering service, such that a softwareapplication could query a device at a known address for other devices.

Devices supporting the register service could be further implemented byallowing them to query other known devices for their known lists. Forexample, a device which knows other devices could query those devicesfor the devices they know about, possibly adding more devices thatregistered with those devices first.

Using a common register server could be further implemented by allowingsuch a server to relay communications to devices it knows about, suchthat even devices which are normally inaccessible from a softwareapplication can be communicated with. Let such a server be called aCommunications Server 4004, which may be include server 1304 or othersuitable server. For example, the computer that a communications serveris running on may be connected to a serial device 4008, which would notbe accessible from another computer. The communications server 4004could then be used to relay external communications, such as networkconnections, to the internal serial device. As another example, thecomputer that a communications server is running on may have access tomultiple network subnets which are isolated from each other. Thecommunications server could then be used to bridge those networks. Thiscould also be applied to bridging local area networks and wide areanetworks. As another example, a device which the communication serverknows about may not support a protocol that an external softwareapplication is required to use. The communication server could thentranslate from one protocol to the other.

Such a communications server could be further implemented by allowingsuch relaying to be performed across multiple such servers. For example,a software application may be on a computer 4010 which is isolatedinside a local area network 4012. This software application couldconnect to a communication server 4006 which bridges onto a wide areanetwork 4014, such as the internet, which could further connect to acommunications server 4004 which bridges onto a remote local areanetwork 4016. This could further relay onto a computer within thatremote local area network, which could be connected to a device viaserial communications.

Using communications servers could be further implemented by keepingquality information for each connection, such that the optimum pathcould be found. For example, a set of communications servers could existsuch that two paths to a single device could exist. One path may requirethree hops, the other two, such that communications over the two hopswould be more reliable and faster than the three. As another example,one path may go through a server which handles more traffic than theother, such that the less used server would be more optimal.

Keeping such quality information could be further implemented byallowing this information to be queried, such that another softwareapplication or server could use this information to choose the bestpath. For example, a software application could collect the pathqualities, and choose to use one path over another. As another example,a server could query other servers' quality information to better updateits own path quality information.

Another possible solution to finding communications parameters could beto provide a software application 4100 which searches for devices, asshown in FIG. 41. One possible implementation of this could be toattempt to connect to each network address accessible from the localcomputer via module 4102. For example, a TCP connection to be attemptedto each network address, and each connection that succeeded could beconsidered accessible. As another example, a connectionless message,such as UDP or ICMP, could be sent to each network address, and eachaddress that responded could be considered accessible. As anotherexample, a web service could be discovered by sending an HTTP GETrequest.

Scanning network addresses could be implemented by automaticallydetermining the range of addresses which are accessible from the localcomputer, by combining the local IP address with the subnet mask.Alternatively, the range of accessible addresses could be determinedfrom the local computers routing table. These ranges of networkaddresses could be further extended by providing a user supplied rangeof network addresses.

Scanning network addresses could be further implemented by first sendinga simple message to determine if a device is there, before attempting tocommunicate to establish the device's identity. For example, an ICMPping could be first sent, and if a response is received, the scan couldfollow up with identifying the type of device discovered. As anotherexample, an ARP request could be made to determine if a MAC address wasknown. As another example, a TCP SYN message could be sent alone, andonly if an ACK was received in response would continue.

Another possible implementation of this could be to open each serialport accessible from the local computer, and attempt to communicate to adevice via module 4104. For example, a software application couldenumerate the serial com ports which are available on the localcomputer, and attempt to open each one in sequence. If the portsucceeded in opening, a message such as Modbus could be sent, and if aresponse was received that connection could be considered accessible.

Scanning serial ports could be implemented by scanning over thedifferent configuration properties of a serial port. For example, serialdevices can communicate at different baud rates, such as 9600, 57600,and 115200, which must be tested independently.

Scanning for devices could be further implemented by including protocolspecific information in the search. For example, for a device thatsupports Modbus, the scan could include trying the different Modbusaddresses, in the range of 1 to 247. As another example, TCP supportsmultiple ports.

Scanning for devices could be further implemented by scanning overmultiple protocols. For example, a device may support Modbus RTU, orDNP, or HTTP web requests.

Determining the communication parameters for a device could beimplemented by using the described methods to fill the known deviceslist. For example, a network scanner could insert each device it foundin the known devices list. Furthermore, it could be used to keep thedevice list up to date.

Using the known device list with a device scanning software applicationcould be further implemented by using the list of known devices toperiodically verify that those devices are still accessible. If thescanner was unable to communicate to a previously valid device, thatconnection could be marked as invalid. Otherwise, it could be marked asconfirmed. Such a test could also be used to detect if the device usingthose communications settings is still the same device. For example,serial ports could easily be reused for multiple devices. As anotherexample, with network devices that use DHCP for their address, theassignment of address could arbitrarily change between them.

Scanning for devices could be further implemented by also queryingdevice information after detecting the device. This information couldthen be inserted into the known devices list, as well as keeping theinformation up to date.

Using the known devices list with the device scanner could be furtherimplemented by automatically creating an unassigned devices location.This location could then be used by the user to easily organize all thedevices which they have not yet assigned to their proper location.

Often the functionality that makes up a software product is split intomultiple software applications. Let this be called a Software Suite.These software applications may be independently developed, withoutthought to them working together. Additionally, they may supportstandalone use, which in some cases may be preferable to standard usage.Such implementations make it difficult to present a consistent, cohesivefeel across the whole software suite.

One possible solution to provide a cohesive feel could be to present asingular frontend to the user of the client device 1408 who isknowledgeable of the entire system and uses each of the individualsoftware applications to perform functionality as required. Let such afrontend be called a Launchpad Application. For example, in a softwaresuite that interacts with devices, three functionalities could beimplemented as individual software applications, such as for polling,log retrieval, and device configuration. A frontend software applicationcould be created that knows about each of the devices involved, andlaunches each of the individual software application with theappropriate command line when required.

Such launched applications could be implemented by allowing them to jumpto specific components of the functionality, bypassing the normalnavigation of the UI. For example, a polling software application couldprovide a means to show a specific polling screen, so that it appearsthat when launched, it is just another window of the callingapplication. As another example, a configuration software applicationcould jump to a specific device configuration page, such ascommunications, without requiring the user to navigate through othersettings. Such a jump could then be used by the frontend softwareapplication to give a more integrated feel to the software.

Such a Launchpad application could be further implemented by dynamicallyenabling and disabling components as they are available to be used bythe user. For example, configuration of a device could be disabled ifthe configuration software is not installed. As another example, the logretrieval action could be disabled if the user does not have the licenseto use it.

Such dynamic enabling could be implemented by downloading and installingsoftware which it does not have installed. For example, the softwareapplications may have only been installed with configuration support.When the user clicks on a polling action, it could download and installthat component. Such dynamic installation could be extended by alsoallowing software components to be removed.

Such dynamic installation could be implemented by requiring a securitykey to perform the download, install, and uninstall. For example, a username and password, or just a password, could be required for the user toinstall new software components.

Such dynamic enabling could be further implemented by providing usergroups, such that only certain users are allowed to use certainfeatures. For example, two groups could be created, a configurationgroup, and a viewer group. The configuration group may have permissionto access the configuration components of the software, and the viewergroup may only have permission to view the polling components of thesoftware.

Such dynamic enabling could be further implemented by providing alicense for each feature, and preventing access until the proper licensekey has been entered by the user. For example, the user may have thelicense to configure device A, but not device B. In such an example, theconfiguration feature for device A would be enabled, but for device B itwould be disabled.

Such a license feature could be further implemented by providing a wayin the software application for the user to purchase the license. Forexample, when the user clicks on a feature for which he or she does nothave the license, the software application could redirect them to awebsite to purchase the license. As another example, it could ask fortheir information, and purchase the license directly. As anotherexample, it could send a request, such as an email, to the sales forceto contact that customer about a license purchase.

Such dynamic enabling could be implemented by providing a visual cue tothe user as to the current state of the feature. For example, a disabledfeature could be grayed out and may not be able to be clicked. Asanother example, a feature which doesn't have a license could display anexclamation icon over it. As another example, a spinning icon could bedisplayed over a feature that is currently being installed.

Another possible solution to a cohesive feel could be for each softwareapplication to use a common source and format of information for displayand usage. For example, using the known devices list to deal with thesame device across multiple software applications. As another example,using the known devices list to display a common grouping of devices.Such a common format could be stored as a database, xml, or other suchformat which could be parsed by both sides.

Using a common source and format of information could be implemented byusing it to move information between software applications. For example,a common format could be used to store device information, allowing theuser to drag a device from a software application which displays devicesfound while scanning, and insert it in another software applicationwhich is used to configure locations. As another example, a commonreference could be used to describe an individual device's log item,allowing the user to drag the item from log viewing software, to be usedin report configuration software.

Such a common source of information could be further implemented byallowing changes to be displayed to the user relatively simultaneouslyin multiple applications. For example, a newly found device could beadded to the known devices, and that device could show up in each of thecurrently running software applications. As another example, assigning adevice to a location could cause that device to disappear from a list ofunassigned devices in another software application. As another example,changing the configuration of what items a device logs could cause thelist of items to view in log view software to update. As anotherexample, an automation process that retrieves logs could cause the databeing viewed in log view software to update.

One possible implementation of this could be for each softwareapplication to periodically check if the known devices list had changed.Another possible implementation of this could be for each softwareapplication to register for notification when changes occur.

Such common display of information could be implemented by providing acommon set of actions that the user could perform on those displays. Forexample, polling software which displays information about a devicecould provide the same actions as device list software or a device scanresults software, which could include polling, log retrieval, andconfiguration. No matter which software the user was in, they would bepresented with the same set of actions they could perform on similarconcepts.

Another possible solution to a cohesive feel could be to configure theUI of each of the individual software applications so that they could berendered inside an arbitrary container, such as another softwareapplication. For example, a software suite that retrieves and displayslog data, but which has external viewer software, could launch theexternal viewer software, and display its UI as an internal frame of thelaunching software.

One possible implementation of this could be to implement the UI of theindividual software applications as HTTP servers, and read and renderthis UI in the launching software as a webpage. For example, pollingsoftware could generate a webpage that could be rendered in the callingsoftware, and contain the layout and values to be displayed. As anotherexample, log retrieval and conversion software could generate a webpagethat contains the progress and status of the conversion.

Implementing the UI as a webpage could be implemented by allowing therendering software to specify the style of the UI, such as with acascade style sheet. For example, a polling page could be made to usethe same color scheme as the rendering application.

Implementing the UI as a web server could be further implemented byallowing the webpage to stand on its own. This would allow the webpageto be used directly from a web browser.

Implementing the UI as a web server may include configuring thetransport over other interfaces, such as but not limited to pipes, diskor ram files, UDP, or shared memory. For example, the webpage for anapplication could be saved to a ram file, to be read periodically by thecalling application.

Implementing the UI as a webpage could be further improved by definingrendering commands specific to the software. For example, a HTML commandcould be defined to display a table of values without requiring <TR> and<TD> elements. As another example, a built in JavaScript function couldbe defined that grabs a file from another location and parses it into alist.

Another possible implementation of embedding the UI in another softwareapplication could be to run a wrapper that transfers the UI contents tobe rendered to the calling application. For example, a remotingprotocol, such as VNC or X-Server, could be used. Such a protocol couldbe rendered by the calling application, and expose the displayed UI ofthe embedded application without redesigning the UI.

In many User Interfaces, it is common to present the user with too muchinformation, or to provide the user with too many options for whataction they should take. Alternatively, it is also common to present theuser with too few options, or hide options in such a way that it is notintuitive as to where to find them, or provide too little information inone location, requiring that they navigate to multiple locations tounderstand what is going on.

One possible solution to this is to use color to draw the user'sattention to pertinent information, while still presenting all theinformation. One possible implementation of this could be to use simple,monotone, or low saturation colors to represent the user interface.Information which was relevant to the action at hand could then berepresented with colors and styles that make it stand out, such as usingbright primary colors, shading, borders, or auras, as to draw theattention of the user. For example, a UI which presented a device listcould represent all the devices in the list using light grays, andrepresent newly added devices in bright blue.

Another possible implementation of drawing the user's attention could beto combine a 2d and 3d appearance, such that information is grouped on2d surfaces, but those surfaces are separated 3-dimensionally. Forexample, a UI could display a device list on one such surface, anddisplay the details of a selected device on another such surface, suchthat the device details surface appears to be floating above the devicelist surface, and the two surfaces floating above the background. Onepossible way to achieve this effect could be to use a drop shadow.Another possible way to achieve this effect could be to use monotonecolors with little to no texture for the 2d surfaces, and use textured,shaded, and contrasted color borders to imply that the surface isfloating.

Floating 2d surfaces could be implemented by making relevant informationfloat above surrounding information. For example, when a user is editinga device's information, that device could be highlighted in the devicelist by raising its entry visually above the other entries. As anotherexample, the input field that the user is entering data to could beraised.

Another possible solution to drawing user's attention is to use motionto highlight the areas requiring attention. One possible implementationof this could be to dynamically change the color of a highlighted item.For example, when a new device is found, it could be highlighted withblue, which could fade to the normal color over time. As anotherexample, when a running script has an error, it could be highlightedwith red, that cycles between light and dark until the error isacknowledged.

Another possible implementation of this could be to visually move activeitems to bring them into focus. For example, when editing a device list,when a device is selected, the device editing surface could be slid intoview from off screen. When the user was done with editing the device,that surface could then be slid off screen. As another example, such asurface could visually rise up from a flat background. As anotherexample, such a surface could visually flip over to present the newinformation.

Using motion could be implemented by providing a smooth motiontransition, so as to not jar the user. For example, a sliding framecould extend from the side of the screen smoothly over a second. Asanother example, a highlight color could fade to the background colorover time.

Another possible solution to drawing user's attention is to usenon-orthogonal shapes and lines to denote areas of focus, while thebackground information remains orthogonal. For example, a popup menucould be represented as a circle. As another example, the border of thecurrently selected item could use beveled corners.

Such a segregation of information could be implemented by arrangingcommon information into frames, which could be visually separated fromother frames, but could be shown simultaneously. For example, a surfacefor a device list, a script list, and a script configuration could beshown, allowing the user to link specific devices to the script they areconfiguring.

Such segregation into frames could be implemented by rearranging theother frames on the user interface to make room, and allow the user tofocus on the new frame. For example, a user interface that displays alocation list could shrink the location list surface to make room for asurface displaying polled data for a device, and a surface for actionsto navigate the polled data. When the user was done with that polleddata, the location list could expand again.

Another possible solution to displaying too many actions to the usercould be to reduce the number of actions displayed on the main userinterface to only those actions commonly used, and then provide a wayfor the user to perform the less common actions by interacting with thecommon one. For example, a device could have the common action ofconnecting, and its less common actions of update firmware, changesettings, and view logs.

One possible implementation of this could be to display a menu of lesscommon actions when the user interacts with a button for a commonaction, such as right clicking it or clicking and holding the button.Another possible implementation of this could be to display additionalactions by sliding the common button to the side, revealing multipleadditional buttons.

With the increase in touch screen devices, it has become difficult topresent contextual information or actions for an item, as the hovercapability of a mouse has disappeared. This can be replaced with a holdaction by the user, with a popup window or menu displayed, but thetraditional drop-down arrangement is often difficult to see with afinger in the way.

One possible solution to this is to present a radial menu, such that thenew information or actions are displayed in a circle around the itemselected. For example, as shown in FIG. 42, three icons 4202, 4204, 4206may be displayed, arranged around the item selected 4200, to representthe actions the user could perform on that item. The action could beperformed by clicking on or touching the icon. As another example,multiple information pop-ups could be displayed, such as a device'sconnection list 4208, firmware versions 4210, errors 4212 and stored loginformation. As another example, and action could be displayed as abubble with text representing the action in it.

A radial menu could be further implemented by displaying a combinationof both information and actions. For example, a menu for a device couldcontain a connect action, a view log action, and display its connectionlist.

A radial menu could be further implemented by visually providing linksbetween the actions and information, and items they are relevant to. Forexample, a device edit surface could have a radial menu which provides aconnect action, linked to the displayed connection string on the editsurface. As another example, a device list surface could have a radialmenu which displays a link to the device actions are performed on.

A radial menu could be further implemented by allowing for radial menuitems to have radial menus of their own. For example, a connection menuaction could have the list of connections as sub-menu items. As anotherexample, a firmware info popup could have a sub-menu with an upgradefirmware action. As another example, clicking on a connection in aconnection list info pop-up could bring up a sub-menu with actions toperform on that connection, such as connecting or removing the entry.

One possible implementation of this could be to arrange the sub-menuaround the menu item in question, creating a tree of menu items. Anotherpossible implementation of this could be to display the sub-menu whenthe main menu item is interacted with, by replacing the original menu.The original menu item selected could be centered between this new menu,and clicking it would return to the original menu.

A radial menu could be further implemented by allowing the user toselect an item by indicating motion in the direction of the item. Forexample, in a touch screen interface, swiping in the direction of themenu item and releasing could select and perform that action.

A radial menu could be further implemented by making the majority of itsrendering transparent, such that only the relevant actions andinformation blocks the surface below it, and as much information of theblocked surface is still visible as possible.

A radial menu could be further implemented by using it even in atraditional mouse environment. As information related to an item iscommonly displayed adjacent to the item, a radial menu would allow theuser to still see those items while making their choice of action.

A radial menu could be further configured by expanding it from the pointof the item selected, using motion to draw the user's attention to themenu.

Further features and implementations of the ScriptManager, KnownDevices,DeviceScan, and Front End of the present disclosure may become apparentto one of ordinary skill in the art from an understanding of thedescription provided herein. It is to be appreciated that the variousfeatures shown and described are interchangeable, that is a featureshown in one embodiment may be incorporated into another embodiment.

While non-limiting embodiments are disclosed herein, many variations arepossible which remain within the concept and scope of the presentdisclosure. Such variations would become clear to one of ordinary skillin the art after inspection of the specification, drawings and claimsherein. The present disclosure therefore is not to be restricted exceptwithin the spirit and scope of the appended claims.

Furthermore, although the foregoing text sets forth a detaileddescription of numerous embodiments, it should be understood that thelegal scope of the present disclosure is defined by the words of theclaims set forth at the end of this patent. The detailed description isto be construed as exemplary only and does not describe every possibleembodiment, as describing every possible embodiment would beimpractical, if not impossible. One could implement numerous alternateembodiments, using either current technology or technology developedafter the filing date of this patent, which would still fall within thescope of the claims.

It should also be understood that, unless a term is expressly defined inthis patent using the sentence “As used herein, the term ‘_(——————)’ ishereby defined to mean . . . ” or a similar sentence, there is no intentto limit the meaning of that term, either expressly or by implication,beyond its plain or ordinary meaning, and such term should not beinterpreted to be limited in scope based on any statement made in anysection of this patent (other than the language of the claims). To theextent that any term recited in the claims at the end of this patent isreferred to in this patent in a manner consistent with a single meaning,that is done for sake of clarity only so as to not confuse the reader,and it is not intended that such claim term be limited, by implicationor otherwise, to that single meaning. Finally, unless a claim element isdefined by reciting the word “means” and a function without the recitalof any structure, it is not intended that the scope of any claim elementbe interpreted based on the application of 35 U.S.C. § 112, sixthparagraph.

What is claimed is:
 1. A system for managing meter connectionparameters, the system comprising: a plurality of meters, wherein eachmeter is configured to measure commodity data representing at least onecommodity being consumed at a location; a communications serverconfigured to enable communications between devices in a network, thecommunications server comprising a scanning module for performing aninitial discovery process to find and identify the plurality of meterson the network by sending a connectionless message to each networkaddress in a range of accessible network addresses on the network, therange of accessible network addresses being determined by combining anIP address of the communications server with a subnet mask, wherein thecommunications server is configured to receive the measured commoditydata from the plurality of discovered meters via the network and storethe measured commodity data, and wherein the communications server isfurther configured to store meter connection parameters related to eachof the plurality of discovered meters; a storage device in communicationwith the communications server via the network, the storage deviceconfigured to receive the meter connection parameters from thecommunications server and store the meter connection parameters; and aplurality of client devices connected to the network, a first clientdevice of the plurality of client devices configured to access thestorage device via the network to receive at least a portion of themeter connection parameters; wherein the meter connection parametersinclude connection information to enable the first client device toidentify at least one discovered meter of the plurality of meters andcommunicate with the at least one discovered meter.
 2. The system ofclaim 1, wherein the meter connection parameters include at least one ofcommunication port information, baud rate, parity, communicationprotocol, meter addressing information, and an IP address.
 3. The systemof claim 1, wherein the communications server is further configured toupdate the meter connection parameters when the meter connectionparameters change.
 4. The system of claim 1, wherein the meterconnection parameters enable a second client device of the plurality ofclient devices to identify a first meter of the plurality of meters whenthe second client device is connected to the first meter using aUSB-to-serial adapter.
 5. The system of claim 4, wherein theUSB-to-serial adapter provides a unique identifier for each meter, theunique identifier configured to assign communication parameters to eachrespective meter.
 6. The system of claim 4, wherein the communicationsserver is configured to identify a previously unidentified meter whenthe USB-to-serial adapter is connected to the first meter on thenetwork.
 7. The system of claim 6, wherein the USB-to-serial adapter isconfigured to send a Modbus message to the communications server whenthe USB-to-serial adapter is connected to the first meter on thenetwork.
 8. The system of claim 1, wherein the communications serverobtains the meter connection parameters by using at least one of a MACaddress and an IP address.
 9. The system of claim 1, wherein thecommunications server is further configured to send the connectionlessmessage using at least one of User Datagram Protocol (UDP), UniversalPlug and Play (UPnP) protocol and/or and Internet Control MessageProtofol (ICMP) ping to elicit a response from a discovered meter. 10.The system of claim 1, wherein one or more of the discovered meters areconfigured to register themselves with the communications server duringan initial registration process.
 11. The system of claim 10, wherein thecommunications server is further configured to determine a properaddress for the one or more discovered meters during the initialregistration process.
 12. The system of claim 10, further comprising arelay device configured to relay communications between thecommunications server and a registered meter.
 13. The system of claim12, wherein the relay device is a communication server.
 14. The systemof claim 12, wherein the relay device is configured to create a bridgebetween one or more local area network and one or more wide areanetworks.
 15. The system of claim 12, wherein the relay device isconfigured to translate one communication protocol to another.
 16. Thesystem of claim 12, wherein the relay device is configured to recordinformation related to a path for enabling communication with one ormore of the registered meters.
 17. A system for providing connectionparameters related to connectivity properties of a plurality of metersin a network, the system comprising: a plurality of meters, each meterbeing configured to measure commodity data representing commodityconsumption; a communications server configured to enable communicationsamong devices in a network, the communications server comprising ascanning module for performing an initial discovery process to find andidentify the plurality of meters by sending a connectionless message toeach network address accessible on the network, the scanning moduledetermines a range of the accessible network addresses by combining alocal IP address of the communication server with a subnet mask, whereina response to the connectionless message indicates that a device isaccessible at a respective network address, and if the response isreceived, the scanning module further communicates with the device toidentify the device as a discovered meter; wherein the communicationsserver is further configured to receive and store meter connectionparameters related to each of the plurality of discovered meters; astorage device in communication with the communications server via thenetwork, the storage device configured to receive the meter connectionparameters from the communications server and store the meter connectionparameters; and a client device connected to the network, the clientdevice configured to receive at least a portion of the meter connectionparameters from the storage device via the network; wherein the meterconnection parameters include connection information to enable theclient device to identify at least one discovered meter of the pluralityof meters and communicate with the at least one discovered meter. 18.The system of claim 17, wherein the scanning module is configured tosearch for the meters by opening each accessible serial communicationport.
 19. The system of claim 1, wherein a response to theconnectionless message from at least one meter indicates that therespective meter is accessible, and if the response is received, thescanning module is further configured to communicate with the at leastone discovered meter to identify a type of the at least one discoveredmeter.
 20. The system of claim 19, wherein the connectionless message isan Internet Control Message Protocol (ICMP) ping.
 21. The system ofclaim 17, wherein the communications server is further configured tosend the connectionless message using at least one of User DatagramProtocol (UDP), Universal Plug and Play (UPnP) protocol and/or anInternet Control Message Protocol (ICMP) ping to elicit the responsefrom a discovered meter.
 22. The system of claim 17, wherein a responseto the connectionless message from at least one meter indicates that therespective meter is accessible, and if the response is received, thescanning module is further configured to communicate with the at leastone discovered meter to identify a type of the at least one discoveredmeter.
 23. The system of claim 19, wherein the type of the at least onediscovered meter includes at least one of an electricity meter, a steammeter, a gas meter and/or a water meter.
 24. The system of claim 22,wherein the type of the at least one discovered meter includes at leastone of an electricity meter, a steam meter, a gas meter and/or a watermeter.
 25. The system of claim 17, wherein the communications server isfurther configured to fill a list of known meters with the meterconnection parameters.
 26. The system of claim 17, wherein the scanningmodule is further configured to periodically verify whether or not eachof the meters is accessible.
 27. A device for providing connectionparameters related to connectivity properties of a plurality of metersin a network, each meter being configured to measure commodity datarepresenting commodity consumption, the device comprising: acommunications device configured to enable communications among devicesin the network; a scanning module for performing an initial discoveryprocess to find and identify the plurality of meters by sending aconnectionless message to each network address accessible on thenetwork, the scanning module determines a range of accessible networkaddresses by combining a local IP address of the communication serverwith a subnet mask, wherein a response to the connectionless messageindicates that a device is accessible at a respective network address,and if the response is received, the scanning module furthercommunicates with the device to identify the device as a discoveredmeter; the communications device is further configured to receive andstore meter connection parameters related to each of the plurality ofdiscovered meters; and a storage device configured to receive the meterconnection parameters from the communications device and store the meterconnection parameters; wherein the meter connection parameters includeconnection information to enable a client device to identify at leastone discovered meter of the plurality of meters and communicate with theat least one discovered meter.
 28. The device of claim 27, wherein thecommunications device is further configured to send the connectionlessmessage using at least one of User Datagram Protocol (UDP), UniversalPlug and Play (UPnP) protocol and/or an Internet Control MessageProtocol (ICMP) ping to elicit the response from a discovered meter. 29.The device of claim 27, wherein a type of the at least one discoveredmeter includes at least one of an electricity meter, a steam meter, agas meter and/or a water meter.